New onboarding, log identification and fixes
We’ve reached the end of another cycle, and we have plenty of news to share with you.
🆕 New customer onboarding
Starting now, new customers can sign up directly on our website. We know the hardest part is integrating with and understanding the API, so we’ve put together a step-by-step guide to integrating with Trio. We hope you like it!
Here’s the link to sign up and try our onboarding.
🆕 Unique identification in logs
From now on, it will be much easier to find problems and debug questions sent by customers. Every Trio request now carries a header called X-Request-Id, so whenever you spot a problem with a request, send this code to support and we’ll be able to trace everything that happened during the integration.
For more details on how X-Request-Id works, see our documentation.
🧠 Improvements
- The credentials used to create a connection are now available from the institutions endpoint. We’ll keep the documentation available indefinitely;
- After gathering feedback from several customers, we’ve implemented a new design to identify the Sandbox environment in Bridge integrations.
🐛 Bugs
- Fixed an issue with the relationship between a connection and the user who gave consent;
- Fixed an issue that prevented creating connections for the Santander - Business institution: the integration was returning incorrect data because of a new update for fetching credit card information.
Until next time!