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

Shuffle Apps API

The Apps API from Shuffle — 8 operation(s) for apps.

Shuffle Apps API is one of 9 APIs that Shuffle publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, pricing, an engineering blog, and 3 JSON Schemas.

This API exposes 9 operations across 8 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://shuffler.io/api/v1, https://{domain}/api/v1.

9 operations 8 paths 3 schemas 2 DELETE3 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://shuffler.io/api/v1
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Shuffle Apps API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — API key obtained from Shuffle profile settings. Include as: Authorization: Bearer

Paths & Operations 9

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

Apps 9
GET
/apps
List Apps
listApps → 200
DELETE
/apps/{id}
Delete App
deleteApp 1 param → 200
POST
/apps/upload
Upload App
uploadApp body → 200
POST
/apps/search
Search Apps
searchApps body → 200
GET
/apps/authentication
List App Authentications
listAppAuthentications → 200
PUT
/apps/authentication
Create App Authentication
createAppAuthentication body → 200
DELETE
/apps/authentication/{id}
Delete App Authentication
deleteAppAuthentication 1 param → 200
GET
/apps/categories
List App Categories
listAppCategories → 200
POST
/apps/categories/run
Run App Category Action
runAppCategory body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are App (8 properties), AppAuthentication (4 properties), ApiResponse (3 properties). Each schema is shown below with its type and property counts.

AppAuthentication
object
4 properties
App
object
8 properties
ApiResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

shuffle-apps-api-openapi.yml Raw ↑

Other APIs Shuffle publishes across the network.

Shuffle Administration API
Shuffle Datastore API
Shuffle Files API
Shuffle Notifications API
Shuffle Organizations API
Shuffle Triggers API
Shuffle Users API
Shuffle Workflows API
Where this information came from

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