Basiq vs Salt Edge Account Information

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.

Salt Edge Account Information

5,000-plus banks in more than 50 countries, by Salt Edge's own count. Rate limit exceeded returns HTTP 406 RateLimitExceeded, not 429.

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.

Salt Edge Account Information

1. Treat HTTP 406 with error_class RateLimitExceeded as a rate limit and back off; it isn't a content-negotiation error
2. Start with fakebank_simple_xf in country XF; it needs no bank sandbox
3. Sign requests from the start even in Test, so the move to Live doesn't change your client
4. Follow next_page from the meta block rather than building from_id URLs yourself
5. Revoke with PUT /api/v6/consents/{consent_id}/revoke when the user is done