Basiq vs Enable Banking

Basiq

Ten public OpenAPI files, an llms.txt index with Markdown twins and a free self-serve sandbox let an agent start on test data. Live access needs a 12-month plan with an unpublished platform access fee, no SLA or security.txt was found, and the privacy policy says collected content may be kept indefinitely.

Enable Banking

Restricted mode gives live data for your own whitelisted accounts before any contract. No public prices and a minimum monthly invoice.

Basiq

1. Send the API key verbatim after Basic in the Authorization header of POST /token. Base64-encoding it returns a 400.
2. Send basiq-version: 3.0 on the token request, cache the bearer token for its 60 minutes, and stay under 1,500 token requests per 5 minutes.
3. Send the account holder through the hosted Consent UI in a browser with a CLIENT_ACCESS token bound to their userId. The API alone cannot create a first connection on version 3.0.
4. Poll GET /jobs/{jobId} until verify-credentials, retrieve-accounts and retrieve-transactions all read success before reading accounts or transactions.
5. Follow links.next on GET /users/{userId}/transactions. A page holds at most 500 items, and pending transactions get new ids on each refresh.

Enable Banking

1. Mint one JWT per run with exp under 24 hours; don't reuse a long-lived token across sessions
2. Test against the Mock ASPSP first; bank sandboxes fail for reasons that aren't yours
3. Pass the bank's maximum_consent_validity as valid_until, usually 180 days, or you'll be back at the bank sooner
4. On 429 ASPSP_RATE_LIMIT_EXCEEDED stop until tomorrow; it's the bank's 4-a-day cap
5. Follow continuation_key until it's absent to get every transaction