Skip to main content
Platform features are currently in invite-only beta. You can sign up here if you want to be considered for one of our next phases. The open source CLI, the compiler and the standalone generator are not part of the beta and are available now.
Every app that has been built exposes a generic, manifest-driven REST facade. It is the same surface the Cordango frontend uses, so anything the product can do to a record, you can do over HTTP.

​
Base URL

{handle} is the app’s handle, not its id. A GUID also resolves, so older links keep working, but the handle is the address to write down. There is no single shared api.cordango.com. A Cordango instance is your workspace, on your subdomain, or on a host you run yourself.

​
What is on it

The app must have been built. These routes are driven by the manifest, so without one there is nothing to drive them.
GET /api/app/{handle}/openapi.json is generated from your own app’s manifest, so it lists your entities and your fields rather than a generic shape. Point a client generator at that rather than transcribing this page.

​
Errors

Every error carries a stable machine-readable code beside a message rendered in the request’s language. Branch on code, show error.
Where an operation can fail several ways at once, the body also carries codes and errors arrays, and the first entry is repeated under code and error.

​
Status codes

​
no relationship
You have no relationship to this app at all. It answers the same way a genuinely missing app does, on purpose: whether an app exists is not something an unrelated caller gets to learn.
​
the role denies it
You have a relationship, and the roles it grants do not permit this operation.
Read responses drop fields your role may not read. Writes that touch fields your role may not set are rejected rather than silently ignored.