API recipes: common integrations

Practical patterns you can build on the Roldesk API. All endpoints are under https://www.roldesk.com/api/v1.

Keep customers in sync

Pull changes since your last sync and upsert them into your CRM/accounting system:

GET /customers?updated_since=2026-08-01T00:00:00Z&limit=100

Page with next_cursor until has_more is false. To push a new customer into Roldesk, POST /customers. Use an Idempotency-Key so re-runs never duplicate.

Create a work order from an external trigger

When a ticket or form comes in, open a job:

POST /work-orders
{ "priority": "HIGH",
  "problem": { "title": "AC not cooling", "description": "…" },
  "account_id": "…" }

Push invoices into your books

Read invoices as they're created (via the invoice.created webhook or GET /invoices?status=…) and mirror them into your accounting system. Totals are computed by Roldesk, so you can trust subtotal, tax, and total.

Avoid conflicts on updates

When updating a record, include expected_updated_at (the value you last read). If someone changed it first, you'll get a 409 instead of overwriting their edit — re-fetch and retry.

Respect rate limits

Each token allows 100 requests / 10 seconds and 5,000 / hour. Every response includes X-RateLimit-Remaining; back off when it's low. Prefer webhooks over frequent polling.

See the full reference and import the OpenAPI spec into your tools.