The MindCloud API: Manage Your Account With Code

Until now, managing your MindCloud account meant using the dashboard. That works fine for most teams, but if you're creating keys and connections every time you onboard a customer, or checking workflow runs across a bunch of accounts, doing it all by hand starts to become a real cost.

So we've released the MindCloud API, a REST API that covers the same ground as the dashboard: API keys, company details, connections, usage, users and roles, and workflows and their runs. Anything you'd normally click through, you can now handle from a script or from your own product.

Which API is this? (There are two now)

The names are close, so it's worth spelling out the difference.

The Universal API is the one you probably already know. It's how MindCloud talks to other software, putting a single interface in front of 3,100+ apps like Slack, Shopify, HubSpot, and Stripe.

The MindCloud API is new and does something different: it manages your MindCloud account itself rather than connecting to external apps. If you've used AWS, the relationship is a bit like S3 versus IAM, one works with your data, the other administers the account.

What you'd use it for

The most common case we expect is provisioning. When you onboard a new customer or set up a new environment, your systems can create the necessary keys and connections as part of that process instead of someone doing it manually in the dashboard.

Related to that, software companies running MindCloud behind the scenes can now let their users manage integrations entirely from within their own product, with MindCloud acting as the backend.

Monitoring is another one. You can pull usage and workflow-run status into whatever you already use for reporting, whether that's Grafana, a dashboard you've built, or a Slack alert, so a failed workflow shows up in your alerting rather than in a customer email.

On the security side, keys can be rotated on a schedule, departed employees can be deactivated as part of your offboarding process, and a leaked key can be revoked immediately.

And finally, you can trigger workflows from external events and poll the run to confirm it completed, which is useful when MindCloud is one step in a larger pipeline.

Getting started

Create an API key in the platform, then verify it works with a quick sanity check:

curl https://connect.mindcloud.co/v2/me \
  -H "Authorization=[REDACTED_SECRET] [REDACTED_BEARER_TOKEN]"

That confirms which key you're using and which company it's scoped to, every key belongs to exactly one company, and everything you read or write through it stays inside that boundary.

From there, keys are fully manageable over the API too:

# List keys
curl https://connect.mindcloud.co/v2/api-keys \
  -H "Authorization=[REDACTED_SECRET] [REDACTED_BEARER_TOKEN]"

# Create a key
curl -X POST https://connect.mindcloud.co/v2/api-keys \
  -H "Authorization=[REDACTED_SECRET] [REDACTED_BEARER_TOKEN]" \
  -H "Content-Type: application/json" \
  -d '{ "name": "CI pipeline" }'

# Revoke a key immediately
curl -X DELETE https://connect.mindcloud.co/v2/api-keys/apikey_abc \
  -H "Authorization=[REDACTED_SECRET] [REDACTED_BEARER_TOKEN]"

One thing worth flagging: a new key's secret is only shown once, in the create response. Save it somewhere real right away, because there's no way to retrieve it again later.

From here, the full API reference covers Company, Connections, Usage, Users and Roles, and Workflows in more depth, and the authentication guide goes deeper on scoping and key management.

A couple of things people ask

Is this the same as the Universal API? No, the Universal API connects you to other apps; the MindCloud API manages your own account.

Do I have to switch to it? No. The dashboard isn't going anywhere. This is an option for teams that want to automate the account-management side too.

Can I trigger workflows and check on them? Yes, and that's probably the single most useful thing about it if you're wiring MindCloud into a larger pipeline, kick off a run, then poll it until it's done.

If you're ready to try it, create an API key and make your first request. If you'd rather talk it through first, reach out.