API overview
The REST API is the same one the web app, the phone app and the MCP server use. Anything you can do in the product you can do over HTTPS with a session token.
If you want ChatGPT, Claude or Gemini to build and operate apps on your behalf, use the MCP integration instead of calling endpoints yourself.
Base URL#
https://api.autoflowly.com/api
All requests must use HTTPS. Responses are JSON.
Authentication#
Send the bearer token of a signed-in session:
curl https://api.autoflowly.com/api/ai-os/apps \
-H "Authorization: Bearer <token>"
Get a token by calling the sign-in endpoint with an email and password:
curl -X POST https://api.autoflowly.com/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email": "you@example.com", "password": "..."}'
Tokens are short-lived and refreshed with the refresh token the sign-in returns. There is no separate API-key scheme today; if you need one for a server-to-server integration, write to support.
Conventions#
- Identifiers are UUIDs. An app's id is the
mvp_idyou see in its dashboard address. - Timestamps are ISO 8601 in UTC.
- Money always travels with a three-letter currency code.
- Decisions are final: a proposal can be decided once; later decisions are refused.
Errors#
{
"detail": "Description of the error",
"status_code": 400
}
| Code | Meaning |
|---|---|
400 | The request is malformed or a field is invalid |
401 | Missing or expired token |
402 | The action needs a paid plan (for example a second creative render) |
403 | You do not own this resource, or the action is blocked by a policy |
404 | Not found |
409 | Not available yet (for example ad launch before it reaches your account) or a conflicting state |
429 | Rate limit; wait for the Retry-After header |
500 | Something went wrong on our side; retry once, then write to support with the request id |
Rate limits#
Limits are per account, tighter on sign-in and generation, and scale with your plan. Anonymous traffic from one network address shares a bucket, so a burst from an office can hit 429 on sign-in; wait a minute. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers, and a 429 carries Retry-After.
Versioning and change#
Endpoints are stable within a path prefix. New fields are added without notice; fields are removed or renamed only after a deprecation note in What's new. Migrations are expand-first: a response never loses a field in the same release that introduced its replacement.