How to set up Volie AI Assistant integration
You will connect your AI voice assistant platform to Volie so call events, organization routing, and optional outbound webhooks work for each dealership you support.
Before you start
To set up Volie AI Assistant integration, you need:
An active integration agreement with Volie
HTTP Basic Auth credentials issued by Volie for your AI assistant (production, sandbox, or test environment)
A technical contact who can configure HTTPS endpoints on your platform
For warm transfers: the Volie phone number Volie provides for live agent handoffs at each organization
Definitions
These terms appear when you set up Volie AI Assistant integration:
Term | Meaning |
Organization VID | The UUID you send in each event’s |
AI assistant credentials | The HTTP Basic Auth username and password Volie provisions for your integration. Credentials are unique per AI assistant and environment. |
Environment | The Volie record scope for your integration (for example production, sandbox, or test). Use matching credentials and organization VIDs for each environment. |
Steps
Follow these steps to set up Volie AI Assistant integration:
Contact Volie integration support at [email protected] to start onboarding or request credentials for a new environment.
Store the username and password Volie provides securely. Volie does not use API keys or bearer tokens for the AI Assistant Listener — every request must send HTTP Basic Authentication.
Confirm which dealerships (organizations) Volie linked to your AI assistant. For each organization, note the organization VID you will send in event payloads.
Call the Organization Discovery API to refresh your organization list:
GET https://api.volie.com/ai_assistant_api/organizations
Send the same HTTP Basic Auth header you use for call events. The response lists each linked organization’s display name and the vid value to use in event_info.vid.
If your platform needs call-completion or Pulse updates from Volie, ask Volie to register your HTTPS webhook URLs for New Call and/or New Pulse notifications on your AI assistant record.
Complete Volie certification by sending test payloads, supporting a live warm-transfer test call when required, and handling Volie webhook responses gracefully if you use outbound webhooks.
What success looks like
When Volie AI Assistant integration setup is complete, your platform can authenticate to Volie, retrieve organization VIDs, and send a test event that returns HTTP 200 OK with body {"Data":"ok"}. If authentication fails with 401 Unauthorized, confirm you are using the correct username and password for the target environment. If organization lookup returns 403 Forbidden on events, confirm the vid in the payload belongs to an organization linked to your AI assistant.
Limitations
Volie AI Assistant integration has these verified limits:
Credentials are per AI assistant and environment — production credentials do not work in sandbox and vice versa.
Each organization VID must belong to the authenticated AI assistant. Events for unlinked organizations are rejected with
403 Forbidden.Legacy Stella-only webhook URLs (
/stella_ai_listenerand/auto_assistant/stella_ai_listener) are removed. Send all events toPOST https://api.volie.com/ai_listener/events(orPOST https://api.volie.com/auto_assistant_ai_listener/).
Common questions
How do I get Volie AI Assistant credentials?
Volie provisions HTTP Basic Auth credentials during onboarding. Contact [email protected] to request credentials or a rotation for a specific environment.
How do I find the organization VID for a dealership?
Call GET https://api.volie.com/ai_assistant_api/organizations with your AI assistant credentials. Use the vid value for each organization in the event_info.vid field when you send call events to Volie.
Can I register webhook URLs myself?
Volie registers New Call and New Pulse webhook URLs on your AI assistant record during onboarding. Contact [email protected] to add or change outbound webhook endpoints.
Related articles
How to send AI call events to Volie