REST API
Errors and limits
What the status codes mean, how errors look, and the limits that apply to the API and the MCP server.
Errors
Errors return JSON with a readable detail, such as {"detail": "We couldn't find that diagram."}. MCP tools return the same words as a tool error, so your AI tool can fix its request.
400- The request can't be read.
401- The key is missing, wrong or revoked.
402- Your plan's limit is reached, such as the number of diagrams on Free.
403- The key's person can view the diagram but not change it.
404- The diagram doesn't exist, or the key can't reach it (another workspace, or not shared).
409- Too many additions are waiting to be drawn: open the diagram once, then add more.
413- The diagram would be too large.
422- A field is missing or not allowed, such as an unknown format.
423- Main is protected: propose a change instead.
429- Too many requests. Wait and try again; the Retry-After header says how long.
Limits
- 120 requests a minute per account, across the API and the MCP server.
- 30 new diagrams an hour per account.
- 200,000 characters of source per request.
- Up to 20 additions can wait on one diagram before it's opened and drawn.
- Diagrams made through the API and MCP count toward your plan like any other. See Pricing.
Stuck, or missing something? Contact us.