How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Flipdish

Flipdish Hydra API

Operations for Hydra.

Documentation Provider Profile APIs.io OpenAPI GitHub

Flipdish Hydra API is one of 85 APIs that Flipdish publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Hydra. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 24 operations across 22 paths, and defines 22 schemas. It is described by OpenAPI 3.0.3, at version v1.0.

Requests are made against a single base URL, https://api.flipdish.co.

24 operations 22 paths 22 schemas 3 DELETE10 GET11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1.0
Base URL
https://api.flipdish.co
Authentication
OAuth 2.0
Contact
Flipdish Support
Resource Areas
1

Authentication & Security 1

Flipdish Hydra API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the implicit and clientCredentials flows, exposing 1 scope. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0. Implicit grant for first-party portal apps; client credentials grant for server-to-server App Store apps (exchange Client ID + Secret Key for a bear…

Paths & Operations 24

Across 22 paths, the API surfaces 24 operations — 3 DELETE, 10 GET, 11 POST. Each is listed below with its method, path, parameters, and response codes.

Hydra 24

Operations for Hydra.

GET
/api/v1.0/hydra/settings
Flipdish Get Settings
GetSettings → 200400401403404500
GET
/api/v1.0/hydra/ably_token
Flipdish Get Ably Token
GetAblyToken → 200400401403404500
GET
/api/v1.0/hydra/registration
Flipdish Get Registration
GetRegistration → 200400401403404500
GET
/api/v1.0/{appId}/emvterminals
Flipdish HydraGet Emvs for App Id
Hydra_GetEmvsForAppId 1 param → 200400401403500
POST
/api/v1.0/{appId}/emvterminals
Flipdish HydraCreate Emv
Hydra_CreateEmv 1 param body → 200400401403500
GET
/api/v1.0/{appId}/hydra/emvterminal
Flipdish Get EMV Terminal Details
GetEMVTerminalDetails 1 param → 200400401403404500
GET
/api/v1.0/{appId}/kiosksettings/{deviceId}
Flipdish Get Kiosk Settings
GetKioskSettings 2 params → 200400401403500
POST
/api/v1.0/{appId}/kiosksettings/{deviceId}
Flipdish Update Kiosk Settings
UpdateKioskSettings 2 params body → 200400401403500
GET
/api/v1.0/{appId}/kioskcashsettings/{deviceId}
Flipdish Get Kiosk Cash Payment Settings
GetKioskCashPaymentSettings 2 params → 200400401403500
GET
/api/v1.0/{appId}/hydra/emvorderstate/{orderId}
Flipdish Get Emv Order State
GetEmvOrderState 2 params → 200400401403404500
GET
/api/v1.0/{appId}/hydra/{deviceType}/{deviceId}
Flipdish Get Attached Device
GetAttachedDevice 3 params → 200400401403404500
GET
/api/v1.0/{appId}/hydra/{deviceType}/list
Flipdish Get Attached Devices
GetAttachedDevices 7 params → 200400401403404500
POST
/api/v1.0/{appId}/hydra/registration
Flipdish Register
Register 1 param body → 200400401403404500
POST
/api/v1.0/{appId}/hydra/cancelemvpayment/{orderId}
Flipdish Cancel Emv Payment
CancelEmvPayment 2 params → 200400401403404500
POST
/api/v1.0/{appId}/hydra/{deviceId}/attach/{storeId}
Flipdish Attach Store to Terminal
AttachStoreToTerminal 3 params → 200400401403404500
POST
/api/v1.0/{appId}/hydra/{deviceId}/detach/{storeId}
Flipdish Detach Store from Terminal
DetachStoreFromTerminal 3 params → 200400401403404500
POST
/api/v1.0/{appId}/hydra/emvterminal/unassign/{hydraConfigId}
Flipdish Unassign Emv
UnassignEmv 2 params → 200400401403500
POST
/api/v1.0/{appId}/AttachStoreToKiosk/{deviceId}/store/{storeId}
Flipdish Attach Store to Kiosk
AttachStoreToKiosk 3 params → 200400401403404500
POST
/api/v1.0/{appId}/hydra/emvterminal/assign/{hydraConfigId}/{emvTerminalId}
Flipdish Assign Emv
AssignEmv 3 params → 200400401403500
POST
/api/v1.0/hydra/{deviceId}/login
Flipdish Login with Device Id
LoginWithDeviceId 3 params → 200400401403404500
POST
/api/v1.0/{appId}/kioskupdatecashsettings
Flipdish Update Kiosk Cash Visibility Settings
UpdateKioskCashVisibilitySettings 3 params → 200400401403404500
DELETE
/api/v1.0/{appId}/emvterminals/{id}
Flipdish HydraDelete Emv
Hydra_DeleteEmv 2 params → 200400401403500
DELETE
/api/v1.0/{appId}/hydra/{deviceId}/registration
Flipdish Un Assign
UnAssign 2 params → 200400401403404500
DELETE
/api/v1.0/{appId}/DetachStoreFromKiosk/{deviceId}/store/{storeId}
Flipdish HydraDetach Store from Kiosk
Hydra_DetachStoreFromKiosk 3 params → 200400401403404500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are HydraDeviceDetails (12 properties), HydraConfig (7 properties), EmvTerminal (6 properties), EmvTerminalWithAssignments (6 properties). Each schema is shown below with its type and property counts.

EmvTerminal
object
EMV Payment Terminal
6 properties
RestApiResult_PaymentTerminalDetails_
object
Rest api result
1 property 1 required
RestApiResult_KioskSettings_
object
Rest api result
1 property 1 required
FlipdishError
object
Standard Flipdish API error response. Errors are returned as a JSON object with a human-readable message and a programmatic error code (see https://developers.…
1 property
RestApiArrayResult_EmvTerminalWithAssignments_
object
Rest api array result
1 property 1 required
RestApiPaginationResult_HydraDeviceDetails_
object
Rest api pagination result
4 properties 4 required
RestApiResult_HydraStatus_
object
Rest api result
1 property 1 required
RestApiArrayResult_KioskCashPaymentSettings_
object
Rest api array result
1 property 1 required
KioskCashPaymentSettings
object
Get Cash Payment Settings for a UserId
2 properties
PaymentTerminalTransactionDetails
object
Details of Payment Terminal Transaction
6 properties
PaymentTerminalDetails
object
Details of Payment Terminal
4 properties
RestApiResult_PaymentTerminalTransactionDetails_
object
Rest api result
1 property 1 required
HydraDeviceDetails
object
Hydra device details
12 properties
RestApiResult_HydraDeviceDetails_
object
Rest api result
1 property 1 required
KioskSettings
object
Kiosk level settings
2 properties
HydraRegistrationRequest
object
Hydra registration result
3 properties 2 required
DeviceSettings
object
Device settings for Hydra
3 properties 3 required
HydraConfig
object
Hydra configuration
7 properties 3 required
EmvTerminalWithAssignments
object
EMV Payment Terminal
6 properties
HydraStatus
object
Hydra status
6 properties 2 required
RestApiResult_HydraConfig_
object
Rest api result
1 property 1 required
HydraStoreData
object
Store Data
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flipdish-hydra-api-openapi.yml Raw ↑

Other APIs Flipdish publishes across the network.

Flipdish Accounts API
AE Profile APIs.io
Flipdish Address API
AE Profile APIs.io
Flipdish Apm API
AE Profile APIs.io
Flipdish Apps API
AE Profile APIs.io
Flipdish AppStore API
AE Profile APIs.io
Flipdish AppStoreConfigurations API
AE Profile APIs.io
Flipdish AppStoreDeveloper API
AE Profile APIs.io
Flipdish AppStoreEntitlements API
AE Profile APIs.io
Flipdish AuditLogs API
AE Profile APIs.io
Flipdish AuthorizationTokens API
AE Profile APIs.io
Flipdish BankAccount API
AE Profile APIs.io
Flipdish Campaigns API
AE Profile APIs.io
#Hydra
← Back to F APIs
API Details
ID
flipdish:flipdish-hydra-api
Base URL
https://api.flipdish.co
Docs
https://developers.flipdish.com/reference
Provider
Flipdish
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=flipdish-hydra-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/flipdish-hydra-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Flipdish Hydra API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.