Read and write everything in your workspace: partners, deals, account mappings, organisations, users and webhooks. Push partner data into your warehouse, register deals from your own portal, or wire Airstride into whatever your revenue team already runs on.
A REST API with the boring parts done properly, so your integration keeps working after you have moved on to something else.
Generate a key in workspace settings and send it in the X-API-Key header. Keys are scoped to your organisation, and you can list, create and revoke them through the API itself.
Pin your integration with the Airstride-Version header, the same way Stripe does it. Deprecated versions keep working and announce themselves in the response headers, so you migrate when it suits you.
The whole surface is described by a spec you can download and generate clients from. The hosted reference lets you send a real request from the page and copy the snippet in Shell, Ruby, Node.js, PHP or Python.
Standard HTTP status codes with a JSON body carrying error and message. Every response reports X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, so backing off is a header read rather than a guess.
Nothing to install and no OAuth dance. A key and a version header is the whole setup.
Go to Workspace Settings, then API Keys, and create a key. Copy it straight away. The token is only shown once.
X-API-Key: sk_live_...Pin the version. If you leave the header off, you get the oldest supported version, which is rarely what you want.
Airstride-Version: 2026-03-01Call an endpoint. Start with your partner list to confirm the key and version are both good.
curl https://app.airstride.ai/api/partners \
-H "X-API-Key: sk_live_..." \
-H "Airstride-Version: 2026-03-01"From sourcing and mapping through to deal management and event delivery. Every endpoint, its parameters and a runnable example live in the reference.
Create, update and enrich partner records, then filter the ecosystem by tier, region, fit score or any field you sync from your CRM.
Register co-sell deals, move them through stages, and patch status as your CRM changes. This is the group most integrations start with.
Kick off a mapping run from a CSV or a CRM sync, read the overlapping and net-new accounts, and manage the history of every run.
Subscribe to events instead of polling. Verify a subscription, inspect delivery attempts, and retry any delivery that failed.
Read and update your organisation profile, list members and invitees, and invite new people. The API key decides which organisation you are acting on.
View and update user profiles, change a person's role, and remove access when someone leaves.
Manage the API keys themselves. Rotate a key on a schedule, or issue a separate key per integration so you can revoke one without breaking the rest.
Subscribe an endpoint of yours to the events you care about. Deliveries are logged with their status, and you can retry any one that failed without replaying the rest.
Versions have a documented lifecycle, and failures come back in a shape you can branch on.
A version is current while it is the one we recommend, deprecated once a newer one ships, and sunset when it stops answering. Deprecated responses carry a Deprecation header and, where one is set, a Sunset date, so a monitor can catch it long before anything breaks.
Current version: 2026-03-01
Every failure returns the same JSON body, so one handler covers the lot.
{
"error": "NOT_FOUND",
"message": "Resource not found"
}The interactive reference has every endpoint with a Try It panel and copyable client code. If you would rather not write an integration at all, the MCP connector puts the same data inside Claude and other assistants, and the native integrations cover Attio, folk, Zoho and the rest of the CRM stack out of the box.