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

Flipdish CardReaders API

Operations for Card Readers.

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

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

This API exposes 13 operations across 13 paths, and defines 14 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.

13 operations 13 paths 14 schemas 2 DELETE3 GET8 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
Resource Areas
1

Authentication & Security 1

Flipdish CardReaders 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 13

Across 13 paths, the API surfaces 13 operations — 2 DELETE, 3 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

CardReaders 13

Operations for Card Readers.

GET
/api/v1.0/{appId}/stripeterminal/connectiontoken
Flipdish Get Stripe Connection Token
GetStripeConnectionToken 1 param → 200400401403500
GET
/api/v1.0/{appId}/payments/terminals/stripe/{readerId}
Flipdish Card ReadersGet Reader
CardReaders_GetReader 2 params → 200400401403500
GET
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/status
Flipdish Get Bluetooth Terminal Status
GetBluetoothTerminalStatus 2 params → 200400401403500
POST
/api/v1.0/{appId}/stripeterminal/location
Flipdish Generate Stripe Terminal Location
GenerateStripeTerminalLocation 1 param body → 200400401403500
POST
/api/v1.0/{appId}/payments/terminals/stripe/register
Flipdish Register Stripe Terminal
RegisterStripeTerminal 1 param body → 200400401403500
POST
/api/v1.0/{appId}/payments/terminals/stripe/{readerId}/cancel_action
Flipdish Cancel Reader Action
CancelReaderAction 2 params → 200400401403500
POST
/api/v1.0/{appId}/payments/terminals/stripe/{readerId}/processPaymentIntent
Flipdish Initiate Reader Process Payment Intent
InitiateReaderProcessPaymentIntent 2 params body → 200400401403500
POST
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/{terminalType}/pair
Flipdish Initiate Kiosk Bluetooth Pairing Mode
InitiateKioskBluetoothPairingMode 3 params → 200400401403500
POST
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/{terminalType}/cancelUpdate
Flipdish Cancel Currently Initiated Bluetooth Device Update
CancelCurrentlyInitiatedBluetoothDeviceUpdate 3 params → 200400401403500
POST
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/{terminalType}/installUpdate
Flipdish Initiate Kiosk Bluetooth Update Install
InitiateKioskBluetoothUpdateInstall 3 params → 200400401403500
POST
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/{terminalType}/checkForUpdate
Flipdish Initiate Bluetooth Terminal Device Update Check
InitiateBluetoothTerminalDeviceUpdateCheck 3 params → 200400401403500
DELETE
/api/v1.0/{appId}/payments/terminals/stripe/unregister
Flipdish Un Register Terminal
UnRegisterTerminal 1 param body → 200400401403500
DELETE
/api/v1.0/{appId}/cardreaders/kiosk/{deviceId}/bluetooth/unpair
Flipdish Unpair Currently Paired Bluetooth Device
UnpairCurrentlyPairedBluetoothDevice 2 params → 200400401403500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are CardReader (8 properties), BluetoothTerminalStatus (7 properties), ReaderActionStateInfo (4 properties), GeoPointRequest (2 properties). Each schema is shown below with its type and property counts.

StripeTerminalConnectionToken
object
Stripe Terminal Connection Token
1 property
RestApiResult_StripeTerminalConnectionToken_
object
Rest api result
1 property 1 required
RestApiResult_CardReader_
object
Rest api result
1 property 1 required
CardReaderRegistrationRequest
object
Card reader registration request
2 properties 1 required
RestApiResult_BluetoothTerminalStatus_
object
Rest api result
1 property 1 required
ReaderActionStateInfo
object
Card reader state information
4 properties
StripeTerminalLocation
object
Stripe Terminal Private Key
1 property
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
UnRegisterCardReaderRequest
object
Un-Register card reader request
2 properties 2 required
ProcessPaymentIntentRequest
object
Initiate card reader Payment process request
1 property 1 required
CardReader
object
Card reader
8 properties
GeoPointRequest
object
Terminal location request
2 properties
RestApiResult_StripeTerminalLocation_
object
Rest api result
1 property 1 required
BluetoothTerminalStatus
object
Status of the bluetooth terminal
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flipdish-cardreaders-api-openapi.yml Raw ↑

Other APIs Flipdish publishes across the network.

Flipdish Accounts API
Flipdish Address API
Flipdish Apm API
Flipdish Apps API
Flipdish AppStore API
Flipdish AppStoreConfigurations API
Flipdish AppStoreDeveloper API
Flipdish AppStoreEntitlements API
Flipdish AuditLogs API
Flipdish AuthorizationTokens API
Flipdish BankAccount API
Flipdish Campaigns API
Where this information came from

This is an independent, third-party profile of Flipdish CardReaders 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.