A resource model that mirrors the work
The API contract is being designed around the records teams already use: organizations, clients, invoices, line items, and payment events.
Developer platform
GET /v1/invoices/inv_01J9...
Authorization: Bearer ci_live_••••
{
"status": "sent",
"currency": "INR",
"amount_due": 56640,
"payment_url": "https://…"
}Why a preview
The API contract is being designed around the records teams already use: organizations, clients, invoices, line items, and payment events.
Planned credentials will be scoped to a workspace. Integrations should never need to infer which organization owns a record.
The planned event model centers on meaningful changes such as an invoice becoming paid, rather than asking teams to poll blindly.
The expected flow
An integration begins with an explicit organization context rather than a hidden default.
Use a stable client record so billing history stays connected to the right relationship.
Pass line items, tax treatment, dates, and terms in a format that can be reviewed before it is sent.
Receive an event when a verified payment changes the invoice state.
Availability
There is no public key issuance and no published integration contact channel yet, so this page does not ask you to write to one. When API access opens it will be announced in the changelog, alongside the endpoints and the credential model it ships with.
Want to use CloudInvoice while the API is being designed?
The web app is the supported way to invoice today, and it is free to start.