Regal is a New York City-based AI Agent Platform purpose-built for contact center operations. The Regal platform lets enterprises design, test, deploy, monitor, and continuously improve AI Phone Agents, SMS Agents, Chat Agents, and WebRTC Voice Agents for inbound and outbound use cases including sales, customer support, scheduling, collections, and lead qualification. The product surface includes an Agent Builder (no-code prompts, actions, knowledge base, variants, languages, LLM models), a Sales Dialer, Journey Builder for orchestrating multi-channel customer experiences, Conversation Intelligence for QA and analytics, and a Copilot that automates agent design. Regal exposes a public REST API spanning a Custom Events ingest endpoint (events.regalvoice.com/events) for contact and event ingestion plus a v1 management API (api.regal.ai/v1) covering Branded Phone Numbers, Business Profiles, Active Phone Numbers, Campaigns, Dispositions, and outbound SMS message sending. The platform also publishes 40+ reporting webhook event types covering calls, SMS, MMS, email, voicemail, agent activity, contacts, and journey state, plus a Custom Actions framework that lets voice agents call out to customer-owned HTTP endpoints during conversations. Regal integrates natively with Segment, mParticle, HubSpot, Salesforce, Zendesk, Kustomer, Klaviyo, Braze, Marketo, Customer.io, Iterable, Microsoft Dynamics 365, Zoho, Hightouch, Cal.com, Calendly, Snowflake, S3, Slack, Microsoft Teams, Five9, Talkdesk, and 8x8.
APIs.json: https://raw.githubusercontent.com/api-evangelist/regal-ai/refs/heads/main/apis.yml
- Position: Consuming
- Access: 3rd-Party
- AI
- AI Agents
- Voice AI
- Contact Center
- Outbound Calling
- Inbound Calling
- Phone Agents
- SMS
- Chat
- WebRTC
- Conversation Intelligence
- Journey Orchestration
- Branded Caller ID
- CCaaS
- CPaaS
- Sales Dialer
- Customer Engagement
- Created: 2026-05-24
- Modified: 2026-05-24
The Regal Events API is a single high-throughput ingest endpoint (POST https://events.regalvoice.com/events) that creates or updates a contact and records a custom event on the contact profile. The body uses a userId plus a traits object (phones, emails, firstName, lastName, address, custom properties) and a top-level name/properties pair describing the event. Identity resolution iterates identifiers in the order primary phone > any other phone > primary email > any other email > userId. A contact must have at least one phone or email to be considered contactable. Authenticated via API key in the Authorization header. Rate limited to 300 requests per second by default. This is the same endpoint that triggers Journeys (and therefore outbound calls, SMS journeys, and reminder sequences) when paired with the correct event name and TCPA opt-in flags.
- Human URL: https://developer.regal.ai/reference/api
- Events
- Contacts
- Identity Resolution
- Ingestion
- Custom Events
- Documentation
- Documentation
- Documentation
- F A Q
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- JSON Schema — JSON Schema
- JSON Schema — JSON Schema
- JSON-LD — JSON-LD
The Branded Phone Numbers API at api.regal.ai/v1/brandedPhoneNumbers lets you register, update, and remove branded caller ID and spam remediation entries on a per-carrier, per-feature basis. POST creates a new registration tying a phoneNumber to a businessProfileId and a carrierFeatures array (with brandingNameShort, brandingNameLong, internalName, reportingGroup, and one of spamRemediation or brandedCallerId enabled). PATCH updates the registration partially. DELETE removes it once all carrier submissions are inactive. The surface is rate limited to 10 requests per second.
- Branded Caller ID
- Phone Numbers
- Trust Center
- Carrier Registration
- Documentation
- Documentation
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- JSON Schema — JSON Schema
The Management API exposes read-only listing endpoints over api.regal.ai/v1 covering Business Profiles (used to drive branded caller ID), Active Phone Numbers in your tenant, Outbound Campaigns, and AI Call Dispositions. These endpoints were introduced in the January 2025 release to enable programmatic onboarding, audit, and reporting against the tenant's configuration without screen-scraping the Regal app UI.
- Business Profiles
- Phone Numbers
- Campaigns
- Dispositions
- Account
- Documentation
- Changelog
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
The Messages API at POST https://api.regal.ai/v1/messages/send delivers outbound SMS messages tied to a Regal SMS campaign. The body requires a to recipient object, a channel value of "sms", and either a campaignId (which supplies default from-number and content) or an explicit from object and content object. Unknown destination numbers are automatically resolved to new contact profiles. Returns 202 Accepted for queued messages and is rate limited to 10 requests per second.
- SMS
- Messaging
- Outbound
- Campaigns
- Documentation
- OpenAPI — OpenAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- JSON Schema — JSON Schema
Regal publishes 40+ reporting webhook event types covering agent activity, call lifecycle (placed, completed, IVR triggered, wrapup), call recording and transcript availability, AI call analysis, task reservations, SMS lifecycle (queued, sent, received, failed, undelivered, conversation completed), MMS, email, voicemail (recording and transcript availability, completion), contact lifecycle (created, subscribed, unsubscribed, attribute and phone/email edits, experiment assignment), scheduled callbacks and reminders, custom tasks, custom objects, and cancel-all-automated-tasks signals. Each event carries a common envelope (userId, traits, name, eventId, properties, originalTimestamp, eventSource) plus event-specific properties. Webhooks must respond within five seconds or the event is dropped (no retries); endpoint changes take up to five minutes to propagate.
- Webhooks
- Events
- Reporting
- Streaming
- AsyncAPI
- Documentation
- Documentation
- AsyncAPI — AsyncAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Portal
- Documentation
- Documentation
- Documentation
- Getting Started
- Documentation
- F A Q
- Support Portal
- Documentation
- Login
- Sign Up
- Pricing
- Plans
- Rate Limits
- Fin Ops
- Blog
- Changelog
- Customers
- Product
- Product
- Product
- Product
- Careers
- Company
- Contact
- Trust Center
- Privacy Policy
- Terms of Service
- YouTube
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Integrations
- Embed
- Embed
- Embed
- Embed
- Single Sign On
- Single Sign On
- Single Sign On
- S C I M
- Vocabulary
- Features
FN: Kin Lane Email: kin@apievangelist.com URL: https://apievangelist.com