clmt_test_ key runs against the sandbox. Every endpoint works, every event
fires, and nothing reaches fulfilment or billing. The sandbox is where you
rehearse an integration before a live key ever touches it.
Two worlds
Test and live are separate. An id from one never resolves in the other, the sameIdempotency-Key is a different key in each, and webhook endpoints are
registered per mode. See
Modes and the sandbox.
Making things happen
A test company never advances on its own, because Clemta is not fulfilling it. You advance it withPOST /sandbox/companies/{id}/simulate:
name the event and the fields it needs, and the change is applied exactly as
a live one would be, once-only rules included, with the resulting events
delivered to your test endpoints.
test_mode_only.
The test clock
Renewals, deadlines, and reminders depend on time passing. The test clock lets you move it. There is one clock in test mode, and while it runs, every time-based rule reads from it instead of the real clock.1
Create the clock
It starts frozen at the current time.Creating it again returns the existing clock.
2
Advance it
Move forward to a moment of your choosing. A clock only moves forward, and
at most five years in one call.Every recurring order renews once for each period the jump crosses, at the
price captured on the order. A monthly service advanced a year renews
twelve times.
3
Read or delete it
GET /clock shows where the clock stands. DELETE /clock returns the mode
to real time. Nothing that happened while the clock ran is undone.