Skip to navigation

Advance a test clock

Moves the clock forward, up to 90 days per call, and runs everything that falls due on the way, in order. The clock is advancing until the work is done, then ready, and test_clock.ready fires.

Authentication

AuthorizationBearer

A secret key (rl_sk_test_..., rl_sk_live_...) or a restricted key with limited scopes (rl_rk_test_..., rl_rk_live_...). A restricted key can carry agent: true and an expires_at, and is what a coding agent should hold. Keys end in a checksum so secret scanners can recognize them. People create, roll and revoke keys in the dashboard; GET /v1/api_keys lists them, masked.

Path parameters

test_clock_idstringRequired

The test clock ID (clock_...).

Request

This endpoint expects an object.
frozen_timedatetimeRequired
The new time. Later than the current one, and at most 90 days ahead.

Response

The advancing test clock.
idstring
object"test_clock"
frozen_timedatetime
statusenum
Allowed values:
deletes_atdatetime
livemodefalse
created_atdatetime
namestringOptional

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
409
Conflict Error
429
Too Many Requests Error
500
Internal Server Error