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

Operations for Mobile Apps.

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

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

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

11 operations 10 paths 17 schemas 4 GET7 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 MobileApps 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 11

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

MobileApps 11

Operations for Mobile Apps.

GET
/api/v1.0/mobileapps/{appId}/submission/details
Flipdish Get Submission Details
GetSubmissionDetails 1 param → 200400401403404500
GET
/api/v1.0/mobileapps/{appId}/saleschannel/details
Flipdish Get App Config Sales Channel
GetAppConfigSalesChannel 1 param → 200400401403404500
GET
/api/v1.0/mobileapps/{appId}/submission/{submissionId}/status
Flipdish Get Submission Status
GetSubmissionStatus 2 params → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/submission/{submissionId}/status
Flipdish Update Submission Status
UpdateSubmissionStatus 2 params body → 200400401403404500
GET
/api/v1.0/mobileapps/{appId}/statistics
Flipdish Get Statistics
GetStatistics 2 params → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/submission
Flipdish Submission
Submission 1 param body → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/resubmission
Flipdish Resubmission
Resubmission 1 param body → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/saleschannel
Flipdish Update App Config Sales Channel
UpdateAppConfigSalesChannel 1 param body → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/submission/image
Flipdish Upload Image
UploadImage 1 param body → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/submission/{submissionId}/publish
Flipdish Publish
Publish 3 params → 200400401403404500
POST
/api/v1.0/mobileapps/{appId}/submission/{submissionId}/unpublish
Flipdish Unpublish
Unpublish 3 params → 200400401403404500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are MobileAppsSubmissionStatus (9 properties), MobileAppsStatistics (9 properties), MobileAppsSubmissionDetails (8 properties), MobileAppsSubmission (6 properties). Each schema is shown below with its type and property counts.

MobileAppsSubmissionStatus
object
Mobile Apps Status
9 properties
MobileAppsImage
object
Mobile Apps Image
1 property
MobileAppsSubmissionDetails
object
Mobile Apps form submission
8 properties
RestApiResult_MobileAppsSubmissionDetails_
object
Rest api result
1 property 1 required
RestApiArrayResult_MobileAppsStatistics_
object
Rest api array result
1 property 1 required
RestApiIntegerResult
object
Rest api integer result
1 property 1 required
UpdateMobileAppsSubmissionStatus
object
Update Mobile Apps Status
6 properties
RestApiResult_AppConfigSalesChannel_
object
Rest api result
1 property 1 required
RestApiResult_UpdateMobileAppsSubmissionStatus_
object
Rest api result
1 property 1 required
MobileAppsSubmission
object
Mobile Apps form submission
6 properties 3 required
RestApiResult_MobileAppsSubmissionStatus_
object
Rest api result
1 property 1 required
RestApiResult_MobileAppsSubmission_
object
Rest api result
1 property 1 required
AppConfigSalesChannel
object
App Config Sales Channel
4 properties
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
RestApiResult_MobileAppsImage_
object
Rest api result
1 property 1 required
RestApiResult_RestApiIntegerResult_
object
Rest api result
1 property 1 required
MobileAppsStatistics
object
Mobile Apps Statistics
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flipdish-mobileapps-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 MobileApps 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.