Durooj API guide
Start with a read request, then test changes on sample data. Keep API keys out of browser code.
Authentication
Create a key in organization/integration settings. Send it in the API-KEY header over HTTPS. Never share a key in a URL or public log; revoke it if exposed.
Open related pageBase URL
Resources start at https://durooj.com/2.0/ . Example: GET /2.0/customers . Use the key for the intended organization; a displayed organization name does not grant authority.
Results and pagination
List resources support page and per_page and return meta information about counts and pages. Use Content-Type: application/json when sending JSON.
Errors and retries
Check the HTTP status and error body. Stop on authentication failures and honor Retry-After for rate limits. Do not repeat writes without checking whether the first request succeeded; use Idempotency-Key where supported.
Compatibility
Some legacy key and header formats remain supported to protect existing integrations. Do not manually rename stored keys or identifiers. Public branding and links use Durooj.
Example read request
curl "https://durooj.com/2.0/customers?page=1&per_page=20" -H "API-KEY: YOUR_API_KEY" -H "Accept: application/json"Replace YOUR_API_KEY only in a secure server environment. This example contains no real key.