Introduction
The Universal API lets you work with many apps through one predictable REST shape.
Every provider has its own details: auth flows, token refresh, pagination styles, filtering syntax, field selection rules, response shapes, and edge cases. MindCloud handles that app-specific work for you. You connect the app account once, then call published actions with the same request pattern across apps.
That is the point: when you authenticate, filter, paginate, sort, or select fields, you do it the MindCloud way. Your code calls MindCloud. MindCloud keeps the connected app authenticated, translates the request for the selected app, and returns a consistent response.
Start here
You need a MindCloud account, a MindCloud API Key, and at least one app connection.
- Sign in to MindCloud.
- Create a MindCloud API Key in API Keys.
- Create or choose a connection in Connections.
- Open the Universal API docs for the app you want to use.
- Choose an action page from the sidebar and copy the request shape for that action.
Keep your MindCloud API Key on your server. Do not ship it in browser code, mobile apps, public repositories, or logs.
First request shape
All action requests use this URL pattern:
https://embedded.mindcloud.co/v1/universal/{appSlug}/{appVersion}/actions/{actionSlug}
For example:
https://embedded.mindcloud.co/v1/universal/slack/latest/actions/list-users
Use the HTTP method that matches the action: GET for read actions, POST for create actions, PUT or PATCH for updates, and DELETE for deletes. You can find the proper HTTP method in the documentation for that action.
What MindCloud handles
MindCloud handles the provider-specific work behind each action:
- app authentication and token refresh
- provider request formatting
- response mapping
- supported field selection, pagination, filtering, and sorting behavior
- provider quirks that would otherwise leak into your application code
Your app should depend on the Universal API contract, not on each provider's private details.
What it's not for
The Universal API is not a raw proxy to arbitrary provider endpoints.
It runs the actions available for the selected app and version. If an action is not listed in the app's action pages, it is not part of that app's Universal API surface.
What to read next
- Read Authentication for MindCloud API Keys,
connectionId, request placement, and HTTP methods. - Read Arguments for passing action-specific inputs.
- Read Pagination, Filtering, and Sorting for list controls.
- Read Field Selection for choosing response fields.
- Read Responses and Errors for response envelopes, metadata, and common failures.