Airtm Bulk Payouts API
# Bulk PayoutsProcess multiple payouts efficiently in a single batch operation. Ideal for payroll, affiliate payments, or mass distributions.## OverviewBulk payouts allow you to submit hundreds or thousands of payout instructions and process them as a coordinated batch, providing better performance and easier management than individual payouts.## How It Works1. **Prepare** your payout data with recipient emails and amounts2. **Submit** the bulk payout request3. **Validation** - System validates all payouts and checks balance4. **Processing** - Individual payouts are processed in parallel5. **Track** progress and handle any failures## Validation Rules### Amount Validation- Minimum amount: $0.01. If the recipient is a US resident, the minimum amount may be larger.- Maximum 2 decimal places allowed- Enterprise fee cannot equal or exceed payout amount (unless negative for bonuses)- Airtm fee cannot equal or exceed net amount (amount - enterprise fee)### Data Validation- Email addresses must be valid format and correspond to active Airtm accounts- Notes field is required and cannot exceed 255 characters- No malicious patterns allowed in text fields (SQL injection protection)- URLs must be valid format when provided### Batch Validation- No duplicate payouts within batch (based on email + amount + notes)- Total batch amount cannot exceed available account balance
Airtm Bulk Payouts API is one of 24 APIs that Airtm publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Bulk Payouts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 3 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.155.0.
Requests are made against 2 base URLs: https://api.enterprise.airtm.com/v2, https://api.stg.enterprise.airtm.com/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Airtm Bulk Payouts API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
Paths & Operations 3
Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Bulk Payouts Process multiple payouts efficiently in a single batch operation. Ideal for payroll, affiliate payments, or mass distributions. Overview Bulk payouts allow you to sub…
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are BulkPayout (10 properties), Pick_CreatePayoutRequest.Exclude_keyofCreatePayoutRequest.commit__ (7 properties), Paginated_BulkPayout_ (3 properties), CreateBulkPayoutRequest (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Airtm 12
Other APIs Airtm publishes across the network.
This is an independent, third-party profile of Airtm Bulk Payouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.