We provide multiple ways to explore the Fintegence Partner API, from instant browser-based testing to full local environment setup. Choose the method that best fits your current integration stage.Integration Paths#
1. Interactive API Explorer (In-Docs)#
Every endpoint in our documentation includes a built-in "Try It" console. This is the fastest way to inspect request and response structures without any local setup.Best for: Immediate sanity checks, schema review, and quick endpoint exploration.
How to use it: Open any endpoint page and use the interactive request panel.
2. Fintegence Public Postman Workspace#
For a more structured testing experience, use our official Postman Workspace. It includes pre-configured collections for Partner Operations and User Operations.Best for: Testing multi-step flows, working across staging and production environments, and sharing requests across your team.
How to use it: Open the workspace directly in your browser or Postman app.
3. Local Collection Export#
If you prefer to use your own API client, such as Insomnia or Bruno, or want to version and automate requests in your own environment, export the collection from Postman and import it into your preferred tool.Best for: Offline work, automated testing, version-controlled request collections, and team collaboration.
How to use it: In the Postman Workspace, open the collection, choose Export, and import the resulting JSON file into your client.
Environment Configuration#
Before making requests, configure your environment variables for either staging or production.| Variable | Stage | Production |
|---|
baseUrl | https://stage-api.fintegence.io | https://api.fintegence.io |
apiKey | Your Staging API Key | Your Production API Key |
externalUserId | Your test external user ID | Your production external user ID |
All requests are authenticated with the x-api-key header. Once you define the apiKey variable in your environment, the collection can reuse it automatically across requests.
Collection Structure#
The collection is organized into two main operational areas.Partner Operations#
Use this section to manage partner-level treasury and settlement logic.Balances & Transaction History: Monitor current balances and historical financial activity.
Currency Exchange: Lock rates, execute exchanges, and track results.
SEPA Transfers: Verify partner bank accounts and manage outbound EUR transfers.
Crypto Withdrawals: Send digital assets to external wallets with fee estimation and compliance checks.
Crypto Deposits: Handle Travel Rule compliance for incoming partner deposits.
Orders: Build payment flows based on locked exchange terms.
Payment Links & Hosted Checkout: Generate payment flows for external payers.
User Operations#
Use this section to manage the end-user lifecycle and user-level financial operations.Onboarding & KYC: Create users and run identity verification flows.
Account Management: Update, suspend, unsuspend, or delete user accounts.
Balances & Transaction History: Track user balances and user-level activity.
Currency Exchange: Execute exchanges using user balances.
SEPA Transfers: Support virtual IBAN verification and user EUR withdrawals.
Crypto Withdrawals: Send user crypto funds to external wallets.
Crypto Deposits: Submit Travel Rule data for incoming user deposits when required.
Internal Transfers: Move funds between partner and user accounts. Direct user-to-user transfers are not supported.
Virtual Cards: Manage card issuance and card-level operations for supported users.
Recommended Integration Approach#
A typical implementation path looks like this:1.
Start with the in-docs explorer to understand request and response structures.
2.
Use the Postman Workspace to validate full flows in staging.
3.
Export collections to your local tooling if you need automated tests or versioned request sets.
4.
Configure webhooks early, because many operational flows are asynchronous.
Many flows in the Fintegence API are asynchronous, including KYC, SEPA transfers, crypto withdrawals, exchanges, orders, and Travel Rule reviews. Your integration should rely on webhooks for real-time updates and use polling endpoints as a backup source of truth.
