Build an integration
Build an integration
Use the licensed API behind your app, CRM or internal service.
The HTTP API is a read-only data connection for integrations covered by a Data Access license. Bring your own application, authentication and destination.
Start with your workflow
| Workflow | Guide |
|---|---|
| Render financial context in an app | Server-side integration |
| Enrich institution accounts | CRM enrichment |
| Load quarterly tables into analytics | Bulk delivery and formats |
| Import a filtered institution list | Pagination and release consistency |
The basic pattern
Your user → your backend → Sloe API → your backend → your user or destination.
Keep the Sloe key on your backend. Cache and retain data only as permitted by your agreement. Authorize your own users before returning licensed data. The API does not provide customer CRM credentials, write into a destination, or grant redistribution rights.
Use the OpenAPI contract for request validation or client generation. Generated client code is a starting point; you still own retries, error handling, access control and data-period labels.