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.
You need a MindCloud account, a MindCloud API Key, and at least one app connection.
Keep your MindCloud API Key on your server. Do not ship it in browser code, mobile apps, public repositories, or logs.
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-usersUse 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.
MindCloud handles the provider-specific work behind each action:
Your app should depend on the Universal API contract, not on each provider's private details.
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.
connectionId, request placement, and HTTP methods.