Yes. Test-mode keys work on a sandbox with sample data, on every plan.

Is the API documented?

Yes: every endpoint, object, webhook event and error code is in the API reference, generated from the OpenAPI file the API is tested against.

API and webhooks integration

The Demurly API, webhooks and MCP

Read and write demurrage records from your TMS, ERP or AP system with the Demurly REST API, get record events by webhook, or connect an AI assistant.

Pro for carriers ($199 a month); free for fuel buyers; test mode free on every plan

Report finished waits from your own systems, send them to buyers, and read statuses and payments.

Approve and dispute charges from your AP workflow, and read records, invoices and statistics.

1An admin creates an API key with the scopes it needs under Settings > API keys. Test keys work on a sandbox, free.
2Webhooks send record events (sent, approved, disputed, paid and more) to your systems, signed and retried.
3AI assistants that support MCP can read your Demurly data with an API key; they can draft comments and disputes, which a person sends in the app.

Is there a sandbox?: Yes. Test-mode keys work on a sandbox with sample data, on every plan.
Is the API documented?: Yes: every endpoint, object, webhook event and error code is in the API reference, generated from the OpenAPI file the API is tested against.

QuickBooks Online

Invoices for carriers, bills for fuel buyers, payments both ways.

NetSuite

Invoices for carriers, vendor bills for fuel buyers, payments both ways.

SAP Business One

A/R invoices for carriers, A/P invoices or drafts for fuel buyers.

PDI Enterprise

Import files for approved charges, and payment registers back.

EDI

214s open and close waits; 210s go out for approved charges.