API Explorer
Explore. Try. Integrate.
A single place to explore the Fabrick APIs: endpoints, parameters, response schemas and, where available, a runner to try the calls directly from the documentation.
What you can do here
Browse endpoints
Path, query params, request body, response schema, examples and HTTP codes.
Try requests
Where available, run requests in the browser to speed up testing and debugging.
Auth per product
Credentials vary: always check the requirements on the specific page.
Sandbox & Production
Base URLs and policies can change between environments and products.
Quickstart
- Select a product from the sidebar (Open Banking / BaaS / etc.).
- Open a page with a Runner (Swagger UI) to browse and try the endpoints.
- Set up your credentials (API key, token, OAuth, mTLS...) following the product instructions.
- Run a call with Try it out and check the response and error handling.
Authentication
Authentication depends on the product and on the integration type. This is a general overview; the details (required headers, flow, permissions) are always given in the documentation of the specific product.
- API Key (dedicated header or
Authorization) - Bearer / access token (application or session token)
- Payment / transaction token (token tied to specific operations)
- OAuth 2.0 (client credentials / authorization code)
- mTLS (client certificates for enterprise/regulated integrations)
Environments
Environments and base URLs can vary between products. In general:
- Sandbox: exploration and end-to-end testing with no impact
- Production: live environment with stricter policies
Runner notes
When you use the Runner (Swagger UI):
- calls are sent from the browser (CORS must allow it)
- watch out for mixed content (docs over HTTPS and APIs over HTTPS)
- some endpoints may be restricted or disabled depending on policy and environment