When integrating the Widget, make sure that:
- Your users register an account with your application first before they access the Okra Widget.
- You customize your own Widget
- You implement the Success and Close callback functions.
Okra strongly recommends that you register your users with your own platform before implementing the widget.
Make sure that your integration can handle, and log the
- 400 and 401 errors
- 500 Errors
- Timeout errors
Okra recommends that you log the
request_id in case you need to reach out to the support team. This ID can help speed up the troubleshooting process.
Make sure that your integration handles:
- 201 Success responses
- Pagination. Read more about how the Okra API returns paginated results in the API reference.
If your integration uses recurrent links, make sure that you:
- Set up a webhook URL in the Dashboard so you can receive webhook events.
- Request a refresh rate of 6 or 12 hours if needed.
- Only send
GETrequests after your receive a webhook event
Make sure that you set webhook URLs in the environment that you are using. Read more about the Okra API's environments in the API reference.
Make sure that your application monitors for
token_required statuses, and prompt your users to update their credentials when needed.
Make sure that any of these potential non-breaking changes in Okra's API does not affect your integration:
- New fields or a different field order in the response body
- Change in the number of characters in a string
- Adding new endpoints
When you are going live with your applicaton, make sure that:
- You are calling the production URL of the Okra API.
- You are using production API keys
Visit the API reference for more best practices about interacting with the Okra API.
Updated 3 months ago