Skip to main content
POST
Schedule retries for a chosen time

Authorizations

Authorization
string
header
required

Bearer token authentication

Body

application/json

The subscription tokens to book, and the time to book them for.

tokens
string[]
required

Subscription tokens. The maximum counts the array as submitted, so maxItems and the server's own refusal agree; duplicates are collapsed after that bound is applied and each subscription is answered once.

Required array length: 1 - 500 elements
Example:
retry_at
string<date-time>
required

When to retry, as an RFC3339 timestamp carrying its offset. The offset is the caller's to state rather than the server's to guess: a bare local hour from a drawer open in one timezone is a different instant on a server running in another.

The time is the operator's choice and nothing else. No model here scores when a charge is likeliest to clear, so the platform neither picks this hour nor adjusts it.

At least 5 minutes ahead — anything nearer is an immediate retry, which has its own endpoint — and no more than 23 hours ahead, the span the retry processor still recognises an operator's booking over.

Example:

"2026-09-15T18:00:00Z"

Response

Every token answered as scheduled, skipped, or failed

One entry per token sent, across three lists.

retry_at
string<date-time>
required

The instant the batch was booked for, in UTC. Echoed so a client states the booked hour from the server's answer rather than from the value it happened to send.

scheduled_tokens
string[]
required

Subscriptions a retry is now booked for.

skipped_tokens
object[]
required

Subscriptions passed over, each carrying why.

failed_tokens
object[]
required

Tokens that resolved to no subscription of the caller's, and subscriptions whose booking write was refused.

meta
object | null
required