What you need from Alianza
Before you can call any Orchestration endpoint, confirm Alianza has provided the following:
| Item | Description |
|---|---|
client_id and client_secret |
OAuth2 credentials for your integration. Used for the Client Credentials grant and as the client identity for the Authorization Code + PKCE grant. |
experienceId |
A UUID that uniquely identifies your Experience. Used in every operation. |
| Experience type | One of POST_CALL, AGENT. Determines which targetType values are valid for this Experience. |
| Source IP allowlist (Alianza → you) | The set of source IPs Alianza will use when sending SIP or SIPREC traffic to your endpoint. |
| OpenAPI specification | The companion openapi.yaml. Available in the Reference section. |
What you provide back to Alianza
The exact onboarding inputs depend on which journey you're building. See:
- Post-Call → What Alianza needs from you — SRS endpoint, codec preferences, mTLS certs, etc.
- Virtual Agent → What Alianza needs from you — SIP endpoint, digest credentials, etc.
Both journeys also ask for a webhook destination URL to receive Experience-related change events, plus the event types you want to subscribe to. See Webhooks.