Skip to main content
The Rain API allows developers to integrate card issuing, transaction management, and collateralized credit solutions into their applications. This page provides general guidelines for using the API, including access instructions and important notes.

Developer notes and tips

Before making requests to the Rain API, itโ€™s helpful to understand a few key details about how our system handles authentication, redirects, and responses. The following sections provide guidelines to ensure smooth integration.

curl and redirects

We proxy our API, so if youโ€™re having trouble testing through curl, try adding the -L flag to follow redirects! Other clientsโ€”such as browsers, backends, and Postmanโ€”should follow these automatically.

Rate limits

The Rain API enforces rate limits to ensure fair usage and prevent abuse. If you exceed these limits, you receive a 429 Too Many Requests response.

Default rate limits

Unauthenticated requests are limited to 1,000 requests per minute based on IP address. Authenticated requests (those with a valid api-key header) are rate-limited at the tenant level. All API calls from your organization share a single bucket, regardless of which endpoints you call.
Subtenants share their parent tenantโ€™s rate limit bucket. All API activity across a parent tenant and its subtenants counts toward the same limit.

Endpoint-specific rate limits

Some endpoints have their own rate limits. On these endpoints, the endpoint-specific limit applies instead of the tenant-level limit, and it is keyed by IP address:

Rate limit overrides

If your integration requires higher rate limits, contact your Rain representative to request a rate limit override for your organization. Changes to rate limit overrides may take up to 10 minutes to take effect due to caching.

Response headers

Each response includes headers to help you monitor rate limit usage:

Handling rate limit errors

If you exceed the rate limit, the API returns a 429 Too Many Requests response. When this happens:
  1. Check the X-RateLimit-Reset header to see when you can retry.
  2. Implement exponential backoff.
  3. Batch requests where possible.
If you need higher rate limits, contact your account manager.

Endpoints

Learn how to authenticate with the API, or select a group of endpoints below to explore further.

Applications

Balances

Cards

Companies

Users

Contracts

Signatures

Disputes

Keys

Transactions

Webhooks

Subscribe to real-time event notifications for cards, transactions, disputes, and more.