Basiq vs GoCardless Bank Account Data

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.

GoCardless Bank Account Data

UK plus every PSD2 country, up to 24 months of history, one API shape for all of them. No public price and no confirmed free plan.

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.

GoCardless Bank Account Data

1. Cache the access token for its 24 hours and use /api/v2/token/refresh/ rather than minting a new pair each run
2. Create the end user agreement before the requisition when you need other than 90 days of history or access
3. Read the per-account rate limit headers; on 429 wait for the account reset time, since some banks allow 4 calls a day
4. Poll /api/v2/accounts/{id}/ until status is READY before asking for transactions
5. Call the REST endpoints directly; the Nordigen SDKs still install but get no fixes