Current REST API

The public developer base is https://api.exepad.com/v1. The current route families are listed below. These are account and integration operations; Studio remains the current app creation and publishing path.

Available routes

Family	Read operations	Write operations
Keys	GET /keys, GET /keys/{keyId}	POST /keys, POST /keys/{keyId}/rotate, DELETE /keys/{keyId}
Billing	GET /billing/wallet, /ledger, /limits, /usage, /pricing, /invoices	POST /billing/topup, /subscribe, /payment-method

Each abbreviated billing path uses the /v1/billing prefix. Billing pricing is public; other listed reads require account authentication and the applicable permission. Billing writes can change payment or subscription settings: use the current account flow or inspect the operation’s current requirements before automating them.

Read account limits

curl --fail-with-body https://api.exepad.com/v1/billing/limits \
  -H "Authorization: Bearer $EXEPAD_KEY"

Legacy reference

The checked-in historical reference describes an earlier API. It is retained for existing links and marked historical. In particular, /v1/apps and /v1/openapi.json are not registered in the current service. Do not use old app lifecycle, streaming build, or deployment examples as current instructions.

Authentication · Billing · Track builds and publishes · Errors