Step 1: Enable the Remote API
Go to Settings
Click Enable Remote API Access
Step 2: Create an Access Token
Navigate to the Access Tokens section in your settings
Click Create new access token
Select the beneficiary this token belongs to
Each token is limited — it will only work for requests tied to the accounts, Pods, and income sources under that beneficiary
You’ll be given a secure key
Important: Save it somewhere safe, it won’t be visible again
Step 3: Obtain API Secrets for Actions
When you create a Rule in Sequence and configure it to be triggered externally, an API Secret will be generated
Copy or note this secret — it’s usually shown once during creation or in the rule details
This secret is required when you trigger that rule via API
Authentication Headers in the Sequence API
The API doesn’t use the standard Authorization: header. Instead, it uses custom HTTP headers:
x-sequence-access-tokenThis is for endpoints that need your user access token (like when you’re doing a GET to retrieve balances or accounts).
Format:
x-sequence-access-token: Bearer YOUR_ACCESS_TOKEN
x-sequence-signatureThis is for endpoints that require a rule’s API secret (like when you’re triggering a rule externally).
Format:
x-sequence-signature: Bearer YOUR_API_SECRET
Key Thing to Know
Some endpoints only need your access token
Others (like rule triggers) need the API secret instead
Never expose these in public or in client-side code — they’re like keys to your bank
Next, we’ll dive into the full API documentation with detailed examples.