Skip to main content
POST
Create a Sarj.ai schedule config (retry policy) for outbound calls

Authorizations

Authorization
string
header
required

API key from your Sarj.ai dashboard. Pass as: Authorization: Bearer

Body

application/json
max_retries
integer
required

Maximum retry attempts after the first call reaches the customer (1-10).

Required range: 1 <= x <= 10
Example:

2

wait_between
string<duration>
required

Wait between attempts, measured from the end of the previous call. Accepts seconds (7200) or an ISO 8601 duration ('PT2H'). 60 seconds to 30 days.

Example:

"PT2H"

enabled
boolean
default:true

Whether calls referencing this config retry. Disabling cancels pending retries at release time.

retry_window
TimeWindow · object | null

Daily window retries may dial in, as start/end wall-clock edges in the config timezone. Omitted, retries dial at any hour.

timezone
string | null

IANA timezone the retry_window is evaluated in. Omitted, the scenario's timezone applies.

Example:

"Asia/Riyadh"

expire_after
string<duration> | null

Stop retrying this long after the first call ended, whichever of attempts/expiry hits first. 1 hour to 7 days (the platform ceiling); omitted, only max_retries and the ceiling bound the group.

Example:

"P3D"

Response

The schedule config was created.

data
PublicScheduleConfig · object
required
meta
ResponseMeta · object

Contains request-level metadata included with every public API response.

Last modified on August 19, 2026