The Orbit API
An app builder API your code can drive
Apps are HTTP resources. POST creates one, PATCH changes it, and a deploy call puts it live. Everything the studio does rides the same model.
Org-scoped tokens; nothing shared by accident.
What the app builder API can do
Plain REST over the same app model every other surface uses.
POST /api/v1/apps
Create an app; the response carries the resource and its id.
PATCH /api/v1/apps/{id}
Change the mutable fields.
GET /api/v1/apps
List what your token can see.
POST /api/v1/apps/{id}/deployments
Launch an app; the same deploy the studio runs.
The API is the same app model
The studio, the CLI, and the API read and write the same app. Your code is not driving a side system; it is another hand on the same wheel.
Questions, answered
How do I authenticate?
With an org-scoped token. Requests act inside that org and nothing else.
What can the API create today?
Apps and deployments, with the same lifecycle the studio uses: create, change, deploy, inspect.
Is there a spec?
The docs carry the current surface. Start at docs.orbitapps.io and the API section.
Does API usage cost anything?
No. Building is free from every surface; AI usage and extra live apps are the two things that cost money.
Treat apps like any other resource
If your code can call an API, it can create, change, and ship an app.
Org-scoped tokens; nothing shared by accident.