While you're integrating the widget, make sure that:
- Your users first register an account with your application before accessing Belvo.
- You implement the Success and Exit callback functions.
- You Implement the widget in update mode to handle links with an
We strongly recommend that you follow the flow of first registering your user with your platform and only then using the widget. This way, you avoid any link duplication errors.
Make sure that your integration can handle, and log the
- 400 and 401 errors
- 500 Errors
- Timeout errors
We ask you to log the
request_id just in case you need to reach out to our support team. With this ID, we can speed up the troubleshooting process and figure out a solution for you.
Can your integration handle:
- 201 Success responses
- 204 Success responses (when you delete some data)
If your integration uses recurrent links, make sure you:
- Set a webhook URL in the dashboard so that you can receive webhook events.
- If needed, requested a refresh rate of 6 or 12 hours
- Made sure you only send GET requests after your receive a webhook event
Please remember that you'll need to set different URLs depending on the environment you're working in.
Does your integration:
- Monitor for
token_requiredlink statuses, and if needed, prompt your users to update their credentials?
If we make the following non-breaking changes to our API, are you sure it won't affect your integration?
- New fields or a different order in the response body
- Change the number of characters for a string
- Add new endpoints
When you are switching to Production, make sure that:
- You are calling the production version of the Belvo API (https://api.belvo.com)
- You are using your Belvo Production API Keys
- You are storing your API keys securely.
Make sure you've subscribed to the following services to be up to date on the status of our API and institutions:
Updated 27 days ago