JomeInvoice V2 API Proxy

JomeInvoice API for submitting and managing e-Invoices.

Quick start

1. Call POST /oauth/token with the API client credentials issued for this environment.
2. Send the returned token as Authorization: Bearer <access_token> on every /api/* request.
3. Preserve the X-Request-ID response header when contacting support. You may also supply your own UUID in that request header.
4. Invoice submission is asynchronous. Store each accepted invoice UUID and poll GET /api/invoices/{uuid} until it reaches a terminal status.

The token endpoint accepts a JSON client-credentials payload. Tokens and credentials are environment-specific; never use production credentials against a non-production server.

Use the standard operations for JomeInvoice invoice payloads. Use the ClearTax operation only when your source payload already follows the ClearTax field conventions; both surfaces target the same authenticated workspace.

Reliability

Only retry requests that are safe for your integration. For 429 responses, wait for Retry-After when it is supplied. For a timeout after creating an invoice, query by the UUID you supplied before submitting again. Error responses include requestId where the standard error envelope is used.

Dates, money, and identifiers

Request dates use YYYY-MM-DD. Timestamps represented as RFC 3339 include an offset or Z; legacy response timestamp fields are documented as strings when they do not. Monetary values are JSON numbers unless a response field explicitly documents a string. UUIDs identify API resources; webhook IDs are ULIDs.

Webhooks

The webhooks section defines the outbound invoices.status_update delivery, including its signed payload and retry policy. Save a webhook client_secret immediately when it is returned: it is shown only at creation or rotation and is not an OAuth client secret.