Build on Dika Ops with a clean, versioned API.
Everything you do in the app, you can do over the API: create orders, move stock, read invoices, sync customers. Endpoints are versioned, responses are predictable JSON, and every call passes the same permission and audit checks as a person.
REST API, piece by piece.
Read and write every record over a documented, versioned API.
What teams use it for.
Push orders from a legacy system or a custom portal straight into the order book.
Pull sales, stock and finance data into your own reporting tools on a schedule.
Small apps for the shop floor or the field team, on top of the same records.
Connected in four steps.
- 01
Create an API token in Settings and pick its scopes.
- 02
Read the reference and try your calls against a test company first.
- 03
Send an Idempotency-Key header with every write so retries stay safe.
- 04
Move to your live company and watch the audit log for the first runs.
REST API, answered.
Which format does the API use?
JSON over HTTPS. Dates follow ISO 8601 and amounts are sent as decimal strings, so money never loses a cent.
Can the API bypass permissions?
No. A token has the permissions of its user or service, checked on every call.
What happens if I retry a request?
With the same idempotency key, the original result is returned and nothing is written twice.
Is there a test environment?
Yes. Beta companies get a test company with sample data to build against.
Run the whole company from one place.
Dika Ops is in closed beta. We onboard a few companies at a time and set everything up with you.