- Setting up API requests to receive customer data
- Setting up Webhooks to receive customer data
| SOLUTION | RECEIVES END USER DATA | DELIVERED TO YOU AUTOMATICALLY | ERRORS ARE HANDLED AUTOMATICALLY |
|---|---|---|---|
| API requests | |||
| Webhooks |
How the two flows compare
Both flows share the same front end: the end user connects their account through Flinks Connect. They only differ in how your back end receives the resulting data:- Standard (API) flow. After the user connects, your server calls the API to pull the data. When /GetAccountsDetail returns
202 OPERATION_PENDING, you poll /GetAccountsDetailAsync every ~10 seconds (up to a 30-minute processing window) until the data is ready. You control when you fetch. See the full Standard Integration walkthrough. - Webhook flow. Flinks pushes the data to a URL you register at onboarding as soon as it’s ready, with no polling. Your endpoint returns HTTP
200to acknowledge receipt. See Webhooks.
Enriched data (Attributes) is always fetched on demand with a separate API call. It is not delivered through webhooks, regardless of which flow you choose.