Your product.
Every connection.
One API.
Connect your customers’ social, ads and email accounts. Build on a common API, SDK and MCP interface—and keep the experience yours.
{
"customer_id": "<CUSTOMER_UUID>",
"provider": "instagram",
"return_url": "https://your-app.com/connected"
}ONE INTEGRATION LAYER.
Build what your customers need.
Let your customers connect their audience.
Build around supported publishing, owned-content analytics and engagement workflows.
- Hosted provider consent
- Connection-specific capabilities
- Trackable execution outcomes
POST /api/v1/projects/{project_id}/executionsAuthenticate with a scoped server key.
Check the connection’s capabilities before requesting an operation.
Implemented scope is documented in the catalog. Live use requires provider approval, deployment configuration and customer consent.
A clear path from here.
- 01
Create your workspace
Keep your team, customer records and scoped API keys in one place.
- 02
Connect with consent
Create a customer, select an enabled provider and send them to hosted consent.
- 03
Build and observe
Call supported operations and follow outcomes through receipts and webhooks.
Only the connections count.
What would your workspace cost?
Count the external accounts your customers connect.
One workspace. One shared allowance. No per-seat connection fee.
per workspace · before tax
- First 3 accounts
- Free
- Additional accounts
- 7 × $1
Provider fees, ad spend and invoice adjustments are separate. This estimate is not a capacity guarantee.
The next connection starts here.
Explore the API, check the scope and build your first workflow.