Developer platform

Build for the invoice moment, not around it.

CloudInvoice is shaping a developer API for teams that want invoicing to fit into their own workflow. The dashboard remains the supported way to work today; public API credentials are not generally available yet. This preview is intentionally clear about the direction and the boundary.
illustrative request shape
GET /v1/invoices/inv_01J9...
Authorization: Bearer ci_live_••••

{
  "status": "sent",
  "currency": "INR",
  "amount_due": 56640,
  "payment_url": "https://…"
}

Why a preview

Honest integration planning starts with the present state.

We would rather show what is ready, what is being designed, and where to ask a question than promise endpoints a team cannot use. You can use CloudInvoice’s web app today, while we validate the right public API surface.

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.

Tenant boundaries are part of the contract

Planned credentials will be scoped to a workspace. Integrations should never need to infer which organization owns a record.

Payment changes deserve events

The planned event model centers on meaningful changes such as an invoice becoming paid, rather than asking teams to poll blindly.

The expected flow

A simple shape for a complex financial handoff.

The public contract will focus on the facts an integration needs to know, with clear state transitions and a durable audit trail.
  1. 01

    Identify the workspace

    An integration begins with an explicit organization context rather than a hidden default.

  2. 02

    Create or reference the client

    Use a stable client record so billing history stays connected to the right relationship.

  3. 03

    Prepare the invoice

    Pass line items, tax treatment, dates, and terms in a format that can be reviewed before it is sent.

  4. 04

    Listen for a real outcome

    Receive an event when a verified payment changes the invoice state.

Availability

No public key issuance in this release.

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.

Building in the open enough to be useful.

  • No invented endpoint availability or artificial API examples presented as live.
  • No sensitive keys in documentation or browser-delivered configuration.
  • A product-led rollout that lets support and auditability mature with the surface area.

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.

Create a workspace