Powens vs Yodlee Core API

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.

Yodlee Core API

A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.

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

Yodlee Core API

1. Get a token with POST /auth/token, sending Api-Version: 1.1 and the end user's loginName as headers and clientId and secret in a form body. Reuse it for up to 30 minutes
2. Use the admin loginName only for administrative calls such as webhook subscriptions. A token made with a user's loginName reads only that user's data
3. In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there
4. Page GET /transactions with skip and top (1 to 500). Without dates it returns the last 30 days, and at most two years with fromDate and toDate
5. A person must link accounts in FastLink 4 first. Then read GET /providerAccounts for link status before GET /accounts
6. Subscribe to DATA_UPDATES or REFRESH webhooks, or poll GET /dataExtracts/events in windows of at most 60 minutes, and do not poll accounts in a loop