Base URL
All API requests target a versioned base URL. Use the production URL for live workloads and the sandbox URL for testing without affecting real data.The Jomioz API is stable at v1. Any backward-compatible changes — such as new optional fields or additional endpoints — are made without a version bump and will never break existing integrations.
Request Format
Send all request bodies as JSON and include aContent-Type: application/json header on every request that carries a body (POST, PUT, PATCH).
Content-Type header.
Response Format
Every successful response is a JSON object wrapped in a consistent envelope. Thedata field contains the resource or array of resources you requested. The meta field carries pagination information when the response is a list.
meta field and place the object directly in data:
Error Responses
When a request fails, Jomioz returns a non-2xx HTTP status code and an error envelope. Thecode field is a machine-readable string you can match programmatically; message is a human-readable explanation; details is an optional array of per-field validation errors.
Versioning
The current API version is v1, embedded directly in the URL path (e.g.,https://api.jomioz.com/v1/resources). When Jomioz introduces breaking changes, a new version (e.g., v2) will be released alongside v1, giving you time to migrate. The deprecation timeline and migration guides will be announced in the changelog before any old version is retired.
Webhooks API
Jomioz exposesPOST /v1/webhooks and DELETE /v1/webhooks/{id} for managing webhook subscriptions programmatically. Full endpoint documentation — including payload shapes, signature verification, and retry behavior — is covered in the Webhooks reference.