Plaid vs Powens

Plaid

Public OpenAPI file, llms.txt with about 250 entries and a Markdown twin of every docs page. No prices before a Production application, and Transactions, Liabilities and Investments bill per Item each month until removed.

Powens

Powens documents a REST API with Markdown docs, cursor pagination, date filters and a hard-delete call for connections, under a French payment institution licence. No OpenAPI file, public price, status page, idempotency key or server SDK was found, and live access needs a signed purchase order.

Plaid

1. Point calls at https://sandbox.plaid.com until you hold a Production secret; request shapes are the same
2. Create a sandbox Item with /sandbox/public_token/create and ins_109508, then /item/public_token/exchange, no Link UI needed
3. Use /transactions/sync with its cursor and back off on 429 RATE_LIMIT_EXCEEDED yourself, since no Retry-After comes back
4. Call /item/remove when the user is done, or subscription products keep billing
5. Send an idempotency_key on /transfer/authorization/create so a retried request can't authorise twice

Powens

1. Ask the owner for the domain name, client ID and client secret from the console. Every call goes to https://{domain}.biapi.pro/2.0
2. Send limit on every transactions list. It is required, at most 1,000, and the next page comes from _links.next.href used as given
3. Enable an account with POST and {"disabled": false} only after the account holder consents. Accounts arrive disabled with no transactions
4. Store the permanent user token as a secret. It does not expire, and the default webhook sends it in the Authorization header
5. Stay under 30 calls a minute in the sandbox and use webhooks in place of polling, as the fair usage policy asks