An overview of the Straddle API structure and usage
The Straddle API is designed around REST principles. Our API features intuitive, resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and utilizes standard HTTP response codes, authentication, and verbs.
You can use the Straddle API in sandbox mode, which doesn’t affect your live data or interact with real banking networks. It’s crucial to use the correct combination of API key and environment URL:
Sandbox API keys must be used with the sandbox environment URL
Production API keys must be used with the production environment URL
Sandbox Environment
https://sandbox.straddle.io
Use this environment for testing and development. It doesn’t affect live data or interact with real banking networks.
Production Environment
https://production.straddle.io
Use this environment for live transactions. Be cautious as this will interact with real banking networks and affect live data.
Authentication to the API is performed via HTTP Bearer Auth. Your API key should be included in the Authorization
header of each request:
The Straddle API accepts JSON-encoded request bodies. Make sure to set the Content-Type
header to application/json
when sending request data.
Responses from the Straddle API are always JSON-encoded. Successful responses include a data
object containing the requested information, while error responses include an error
object with details about what went wrong.
The Straddle API is designed for individual object operations. Bulk updates are not supported, meaning you can work on only one object per request.
Always use HTTPS for API requests to ensure data security.
Include a unique Request-Id
header with each request to help with debugging and tracking.
Use the Correlation-Id
header for requests that are part of a larger operation or transaction.
Implement proper error handling to gracefully manage API responses.
By following these guidelines and understanding the structure of the Straddle API, you’ll be well-equipped to build robust integrations with our platform.
For detailed information on specific endpoints and request/response structures, please refer to the relevant sections of this API reference documentation.
You can also download the raw OpenAPI specification file:
Download OpenAPI Specification