Developers / 05
Custom integrations
When the public API is not enough. Enterprise connectors, quoted by sales. Technology partners start on Build an integration.
When this page applies
enterpriseCustom integrations are an Enterprise sales conversation. They are not a Lite checkout and not a loophole around Acceptable Use. Use them when you have already mapped contacts, calls, messages, and leads on the public API and still cannot write the system of record you must keep.
If you are shipping a connector other customers will use, start as a technology partner on Build an integration. If you only need to resell the floor, that is Channel Partner.
Try the public surface first
included- CRM integrations already on the plan
- Workspace API, messaging API, transcription API
- Webhooks for call.completed, lead.created, export.ready
- avaga-forms.js with no field mapping
- Data export extra, custom reports on Business
Quoted with Enterprise
sales- Custom connectors the public API cannot cover
- SSO / SAML
- Custom SLA and dedicated onboarding
- Security review / BAA
- Multi-entity or multi-brand billing
- Custom agent and number volumes
What we will ask
intake- Which object cannot move today: contact, call, message, lead, recording, or report.
- Whether HubSpot, Salesforce, a CCaaS, or a warehouse is the system of record.
- Whether PHI or a DPA is in scope. If yes, do not send sample audio in email.
- Volume: seats, numbers, and whether you need committed-use pricing.
- Whether this connector is for one workspace or for a partner catalog.
Developer support on the public API stays on every plan. Custom work is scoped after that intake. Screenshots are a guide, not a contract.