Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ibantrack.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Quickstart Guide

All API requests are made to: 
https://api.ibantrack.com/api-v1
This guide walks you through making your first IBAN holder verification request.
1

Get API Credentials

Log in to your Ibantrack Dashboard and retrieve your credentials under Settings > API.
  • Client ID
  • Client Secret
You must have Administrator privileges to view and copy these credentials.Your Client ID & Secret carry significant privileges. Please keep them secure and do not share them.
2

Obtain Access Token

curl -X POST https://api.ibantrack.com/api-v1/oauth2/token \
     -H "Content-Type: application/x-www-form-urlencoded" \
     -d "grant_type=client_credentials" \
     -d "client_id=YOUR_CLIENT_ID" \
     -d "client_secret=YOUR_CLIENT_SECRET"
Response:
{
  "access_token": "eyJhbGciOiJIUzI1NiItOvR5cCI6IkpXVCJ9...",
  "token_type": "Bearer",
  "expires_in": 3600
}
Tokens expire after 1 hour. Cache and reuse tokens until expiration.
Once you have obtained an access token, include it in the Authorization header of every API request.For detailed token management, see Authentication .
3

Make Your First Verification

curl -X POST https://api.ibantrack.com/api-v1/account-holder-verifications \
     -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "account": {
         "iban": "FR7630004000031234567890143"
       },
       "account_holder": {
         "name": "Jean Dupont"
       }
     }'
Successful response:
{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "match"
}
In addition to account holder verification, Ibantrack may provide optional enrichment data derived from the submitted IBAN (Currently available only for French IBANs.
See Enrichment.
4

Interpret the Result

The match_result tells you if the name matches:
ResultMeaning
match✅ Name matches bank records
close_match⚠️ Similar name (review matched_name)
no_match❌ Name doesn’t match
See Match Results for details.

​
Quick Example

# 1. Get access token
curl -X POST https://api.ibantrack.com/api-v1/oauth2/token \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET"

# 2. Verify account holder
curl -X POST https://api.ibantrack.com/api-v1/account-holder-verifications \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "account": {"iban": "FR7630004000031234567890143"},
    "account_holder": {"name": "Jean Dupont"}
  }'

​
Test in Sandbox

Use the sandbox environment to test without real bank calls.
The sandbox_result input parameter forces a specific outcome: 
curl -X POST https://api.ibantrack.com/api-v1/sandbox/account-holder-verifications \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "account": {"iban": "FR7630004000031234567890143"},
    "account_holder": {"name": "Jean Dupond"},
    "sandbox_result": "close_match"
  }'
See the Sandbox page for more details.

​
Response Codes

Ibantrack uses conventional HTTP response codes to indicate the success or failure of an API request.
CodeDescription
200Success: Everything worked as expected.
400Bad Request: The request was unacceptable, often due to missing parameters.
401Unauthorized: No valid client credentials or token provided.
403Forbidden: Insufficient credits to perform the verification.
429Too Many Requests: You have hit the rate limit.
500Server Error: Something went wrong on our end.

​
Rate Limiting

To ensure platform stability and high quality of service for all users, Ibantrack API enforces the following rate limits:
EndpointRate Limit
POST/account-holder-verifications60 requests / minute
GET/account-holder-verifications/{id}120 requests / minute
If your application exceeds these limits, the API will return a 429 Too Many Requests error.
Need higher limits for batch processing or high-volume environments? Contact our support team to discuss a custom plan.

​
Next Steps

Understand Match Results

Learn how to interpret verification results

Full API Reference

All parameters and responses

Sandbox Guide

Test all scenarios

Handle Errors

Retry logic and error codes