Advance your simulation clock
Moves the mode’s simulated time forward to to and runs the time-driven machinery up to it. Every renewal period that comes due before that moment bills, so a monthly order advanced a year bills twelve periods at once. Advancing changes nothing about how new records stamp their own times. It only decides how far “due” has looked.
Authorizations
Your API key, e.g. Authorization: Bearer clmt_test_. Live keys use the clmt_live_ prefix.
Headers
Date-based API version to run this request against.
"2026-08-13"
Body
The moment to advance the simulated world to. Must be after the clock's current simulated_time, at most five years ahead of it per call. Every renewal period due before this moment bills on your ledger during the call, and on a live clock each month boundary crossed drafts that month's statement.
"2027-09-08T00:00:00Z"
Response
The clock at its new simulated time.
Entity name.
clock "clk_0346sFPEvSkJvY8vt14NNw"
The mode this clock simulates. A test clock is always available. On the production API a live clock is refused - it is a sandbox rehearsal tool.
The moment your simulated world has reached. It starts at the real current time when the clock is created and only ever moves forward. Advancing it processes every renewal and billing event that comes due up to this moment.
When the clock was last advanced. Absent until the first advance.