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 Channels API

Operations for Channels.

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

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

This API exposes 12 operations across 10 paths, and defines 11 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.

12 operations 10 paths 11 schemas 3 DELETE6 GET3 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 Channels 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 12

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

Channels 12

Operations for Channels.

GET
/api/v1.0/{appId}/channels
Flipdish Get Channels
GetChannels 1 param → 200400401403500
GET
/api/v1.0/{appId}/channels/{id}
Flipdish Get Channel
GetChannel 2 params → 200400401403404500
GET
/api/v1.0/{appId}/channels/assigned-channels
Flipdish Get Assigned Channels
GetAssignedChannels 1 param → 200400401403500
GET
/api/v1.0/{appId}/channels/available-channels
Flipdish Get Available Channels
GetAvailableChannels 1 param → 200400401403500
GET
/api/v1.0/{appId}/channels/{channelId}/stores
Flipdish Get Stores by Sales Channel
GetStoresBySalesChannel 2 params → 200400401403500
DELETE
/api/v1.0/{appId}/channels/{channelId}/stores
Flipdish Detach All Stores from Sales Channel
DetachAllStoresFromSalesChannel 2 params → 200400401403500
GET
/api/v1.0/{appId}/channels/{channelId}/assigned-storesdeprecated
Flipdish Get Stores Assigned to Channel
GetStoresAssignedToChannel 2 params → 200400401403500
POST
/api/v1.0/{appId}/channels/{channelId}/assign-appId
Flipdish Assign App Id to Sales Channel
AssignAppIdToSalesChannel 2 params → 200201400401403404500
POST
/api/v1.0/{appId}/channels/{channelId}/stores/{storeId}
Flipdish Attach Store to Sales Channel
AttachStoreToSalesChannel 3 params → 200400401403500
DELETE
/api/v1.0/{appId}/channels/{channelId}/stores/{storeId}
Flipdish Detach Store from Sales Channel
DetachStoreFromSalesChannel 3 params → 200400401403500
POST
/api/v1.0/{appId}/channels/assign-storedeprecated
Flipdish Assign Store to Channel
AssignStoreToChannel 3 params → 200201400401403404500
DELETE
/api/v1.0/{appId}/channels/unassign-storedeprecated
Flipdish Unassign Store from Channel
UnassignStoreFromChannel 3 params → 200204400401403404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Channel (6 properties), StoreChannelAssignment (3 properties), StoreItemHeader (2 properties), AppChannelAssignment (2 properties). Each schema is shown below with its type and property counts.

StoreItemHeader
object
2 properties
Response
object
1 property
Channel
object
Channel.
6 properties
StoreChannelAssignment
object
Represents a store that is assigned to a Sales Channel
3 properties
RestApiArrayResult_Channel_
object
Rest api array result
1 property 1 required
RestApiResult_Channel_
object
Rest api result
1 property 1 required
RestApiResult_StoreChannelAssignment_
object
Rest api result
1 property 1 required
RestApiArrayResult_StoreChannelAssignment_
object
Rest api array result
1 property 1 required
RestApiResult_AppChannelAssignment_
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
AppChannelAssignment
object
Describes a ChannelAssignment which is when a AppId is assigned to a Sales Channel
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flipdish-channels-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 Channels 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.