API Reference

Welcome to the Infinite API reference documentation. Our REST API allows you to programmatically manage customers, handle verification workflows, process transfers, and more. We’re also preparing to launch card issuing capabilities - stay tuned!

Base URLs

Environment	Base URL
Sandbox	`https://sandbox.api.infinite.dev`
Production	`https://api.infinite.dev`

CLI and MCP examples

Every endpoint page includes CLI and MCP tabs next to the usual HTTP snippets.

CLI — @infinite_dev/cli. Prefer typed commands (infinite customers list) when available; otherwise use the escape hatch infinite api <METHOD> <path>.
MCP — Infinite MCP Server. The tab is the natural-language prompt for an MCP-connected assistant. MCP is read-only, so write prompts note that the CLI tab executes.

OpenAPI Specification

The complete API specification is available in OpenAPI 3.0 format:

Environment	Swagger UI	JSON Spec
Sandbox	sandbox.api.infinite.dev/api	sandbox.api.infinite.dev/api-json
Production	api.infinite.dev/api	api.infinite.dev/api-json

We recommend generating a typed OpenAPI against the file so you can update the OpenAPI very trivially and regenerate the client.

API Versioning

The Infinite API uses URI versioning. All endpoints are prefixed with /v1/ to indicate the API version.

https://api.infinite.dev/v1/customers

Response Format

All API responses follow a consistent JSON format:

Success Response

{
  "data": {
    // Resource data
  },
  "meta": {
    // Metadata (pagination, counts, etc.)
  }
}

Error Response

{
  "error": "ValidationError",
  "message": "Invalid request parameters",
  "statusCode": 400,
  "details": [
    {
      "field": "email",
      "message": "Invalid email format"
    }
  ]
}

HTTP Status Codes

The API uses standard HTTP status codes:

Code	Description
`200`	OK - Request succeeded
`201`	Created - Resource created successfully
`400`	Bad Request - Invalid request parameters
`401`	Unauthorized - Invalid or missing API key
`403`	Forbidden - Insufficient permissions
`404`	Not Found - Resource not found
`422`	Unprocessable Entity - Validation error
`429`	Too Many Requests - Rate limit exceeded
`500`	Internal Server Error - Something went wrong

Request Headers

Required Headers

Authorization: Bearer sk_live_your_api_key
Content-Type: application/json

Pagination

List endpoints support pagination. Most endpoints use offset-based pagination, while high-volume endpoints (like transfers) use cursor-based pagination.

Offset-Based Pagination

Used by most list endpoints (customers, accounts, etc.). Request

curl "https://api.infinite.dev/v1/customers?limit=20&offset=0" \
  -H "Authorization: Bearer sk_live_..."

Response

{
  "data": [...],
  "total": 150,
  "limit": 20,
  "offset": 0
}

Parameters

limit - Number of items to return (1-1000, default 50)
offset - Number of items to skip (default 0)

Cursor-Based Pagination

Used by high-volume endpoints like transfers for better performance with large datasets. Request

curl "https://api.infinite.dev/v1/transfers?page_size=20&starting_after=txn_abc123" \
  -H "Authorization: Bearer sk_live_..."

Response

{
  "has_more": true,
  "page_size": 20,
  "url": "https://api.infinite.dev/v1/transfers?page_size=20&starting_after=txn_abc123",
  "data": [...],
  "page_next": "https://api.infinite.dev/v1/transfers?starting_after=txn_xyz789&page_size=20",
  "page_prev": null
}

Parameters

page_size - Number of items to return (1-1000, default 50)
starting_after - ID of the last item from the previous page

Data Types

Enums

Enum values use SCREAMING_SNAKE_CASE (e.g., PENDING, IN_PROGRESS, PROOF_OF_ADDRESS). Exception: Payment rails use lowercase (e.g., ach, wire, swift, sepa).

Dates and Timestamps

Dates (without time): YYYY-MM-DD format (e.g., 2026-01-09)
Timestamps (with time): ISO 8601 format with timezone YYYY-MM-DDTHH:mm:ssZ (e.g., 2026-01-09T14:30:00Z)

Country and Currency Codes

Country codes: Two-letter ISO 3166-1 alpha-2 (e.g., US, GB, DE)
Currency codes: Three-letter ISO 4217 (e.g., USD, EUR, USDC)

Filtering and Sorting

Many list endpoints support filtering and sorting:

Filtering

# Filter by status
curl "https://api.infinite.dev/v1/customers?status=ACTIVE"

# Filter by type
curl "https://api.infinite.dev/v1/customers?type=INDIVIDUAL"

# Filter by country
curl "https://api.infinite.dev/v1/customers?countryCode=US"

Sorting

# Sort by creation date (newest first)
curl "https://api.infinite.dev/v1/customers?sort=-createdAt"

# Sort by name (A-Z)
curl "https://api.infinite.dev/v1/customers?sort=customerName"

Idempotency

To prevent duplicate requests, include an Idempotency-Key header with a unique value:

curl -X POST "https://api.infinite.dev/v1/customers/individuals" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Idempotency-Key: unique-request-id-123" \
  -H "Content-Type: application/json" \
  -d '{...}'

Webhooks

Infinite sends webhooks for important events. Configure webhook endpoints in your dashboard to receive real-time notifications. Common webhook events:

customer.created
verification.completed
transfer.processed
invoice.paid

See our Webhooks Guide for implementation details.

Support

Need help with the API?

Check our guides section for common integration patterns
Review error handling best practices
Contact support at support@infinite.dev

​API Reference

​Base URLs

​CLI and MCP examples

​OpenAPI Specification

​API Versioning

​Response Format

​Success Response

​Error Response

​HTTP Status Codes

​Request Headers

​Required Headers

​Pagination

​Offset-Based Pagination

​Cursor-Based Pagination

​Data Types

​Enums

​Dates and Timestamps

​Country and Currency Codes

​Filtering and Sorting

​Filtering

​Sorting

​Idempotency

​Webhooks

​Support