Docs
Lifecycle

Change how eagerly the account stays connected

POST
/v1/accounts/{id}/mode

always_on: stays connected. warm_on_demand: connects on demand (the first order, or a prepare) and goes offline by itself when idle. cold: connects only when you ask.

Takes effect the next time the account is brought online, so the call stays fast and predictable. Switch to always_on and then bring the account online to apply it now.

Authorization

apiKey
AuthorizationBearer <token>

Authorization: Bearer fx_live_<id>_<secret>.

A key is shown once, at creation. We cannot show it again or recover it for you. Keys carry an environment (live or test) in the key itself, so a test key pasted into a production config fails immediately instead of at the worst possible moment.

Scopes are per key. A key without accounts:write can read accounts and nothing else.

In: header

Path Parameters

id*string
Formatuuid

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/accounts/497f6eca-6276-4993-bfeb-53cbbbba6f08/mode" \  -H "Content-Type: application/json" \  -d '{    "mode": "always_on"  }'
{  "data": {    "accountId": "3d07c219-0a88-45be-9cfc-91e9d095a1e9",    "mode": "always_on",    "restingState": "string"  }}