API Keys & REST API

When a program scales, some workflows belong in your own systems. The public REST API lets you read and write partners, commissions, and payouts programmatically, with scoped API keys you control and can revoke at any time.

​

What it does

The public REST API exposes the core objects of your program: partners, commission lines, and payouts. You create an API key, grant it only the scopes it needs, and call the API from your own systems to list, create, and update those records. Keys can be set to expire and revoked instantly, so access stays controlled. This turns Introw into a building block in your stack. RevOps can sync data into a warehouse, finance can push payout updates from another system, and engineering can automate program workflows, all against a documented, scoped API.

​

The problem it solves

Some integrations cannot be click-configured, and that should not mean exporting spreadsheets:

• Custom workflows need programmatic access → A REST API reads and writes partners, commissions, and payouts.
• Broad access is a security risk → Keys are scoped to only the resources they need.
• A leaked key is hard to contain → Keys expire and can be revoked instantly.
• Data is trapped in one tool → The API moves program data into your own systems.

​

From problem to solution

Create a scoped key, build against the documented endpoints, and automate the workflows that belong in your stack. Access stays tight through scopes and expiry, and the CRM remains the source of truth behind it all.

​

Use cases

​

Impact

• Composability - The API is a building block you combine into your own stack.
• CRM-native - Program data stays reconciled to the CRM behind the API.

​

Who it’s for

​

Works with

​

Going deeper