Regal

aid: regal-ai
name: Regal
url: https://raw.githubusercontent.com/api-evangelist/regal-ai/refs/heads/main/apis.yml
description: >-
  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.
tags:
  - 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
kind: contract
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
access: 3rd-Party
position: Consuming
specificationVersion: '0.20'
created: '2026-05-24'
modified: '2026-05-24'
apis:
  - aid: regal-ai:regal-events-api
    name: Regal Events API
    tags:
      - Events
      - Contacts
      - Identity Resolution
      - Ingestion
      - Custom Events
    humanURL: https://developer.regal.ai/reference/api
    properties:
      - url: https://developer.regal.ai/reference/overview
        type: Documentation
      - url: https://developer.regal.ai/reference/api
        type: Documentation
      - url: https://developer.regal.ai/docs/send-custom-event-to-regal
        type: Documentation
      - url: https://developer.regal.ai/reference/faq
        type: FAQ
      - url: openapi/regal-events-api-openapi.yml
        type: OpenAPI
      - url: json-schema/regal-contact-schema.json
        type: JSONSchema
      - url: json-schema/regal-event-schema.json
        type: JSONSchema
      - url: json-ld/regal-ai-context.jsonld
        type: JSONLD
    description: >-
      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.
  - aid: regal-ai:regal-branded-phone-numbers-api
    name: Regal Branded Phone Numbers API
    tags:
      - Branded Caller ID
      - Phone Numbers
      - Trust Center
      - Carrier Registration
    humanURL: https://developer.regal.ai/reference/post-branded-phone-number
    properties:
      - url: https://developer.regal.ai/reference/post-branded-phone-number
        type: Documentation
      - url: https://developer.regal.ai/reference/patch-branded-phone-number
        type: Documentation
      - url: https://developer.regal.ai/reference/delete-branded-phone-number
        type: Documentation
      - url: openapi/regal-branded-phone-numbers-api-openapi.yml
        type: OpenAPI
      - url: json-schema/regal-branded-phone-number-schema.json
        type: JSONSchema
    description: >-
      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.
  - aid: regal-ai:regal-management-api
    name: Regal Management API
    tags:
      - Business Profiles
      - Phone Numbers
      - Campaigns
      - Dispositions
      - Account
    humanURL: https://developer.regal.ai/reference/overview
    properties:
      - url: https://developer.regal.ai/reference/overview
        type: Documentation
      - url: https://www.regal.ai/blog/january-2025-releases
        type: ChangeLog
      - url: openapi/regal-management-api-openapi.yml
        type: OpenAPI
    description: >-
      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.
  - aid: regal-ai:regal-messages-api
    name: Regal Messages API
    tags:
      - SMS
      - Messaging
      - Outbound
      - Campaigns
    humanURL: https://developer.regal.ai/reference/send-message
    properties:
      - url: https://developer.regal.ai/reference/send-message
        type: Documentation
      - url: openapi/regal-messages-api-openapi.yml
        type: OpenAPI
      - url: json-schema/regal-message-schema.json
        type: JSONSchema
    description: >-
      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.
  - aid: regal-ai:regal-reporting-webhooks
    name: Regal Reporting Webhooks
    tags:
      - Webhooks
      - Events
      - Reporting
      - Streaming
      - AsyncAPI
    humanURL: https://developer.regal.ai/docs/reporting-webhooks
    properties:
      - url: https://developer.regal.ai/docs/reporting-webhooks
        type: Documentation
      - url: https://support.regal.ai/hc/en-us/articles/5725272620187-How-to-Use-Journey-Webhooks
        type: Documentation
      - url: asyncapi/regal-reporting-webhooks-asyncapi.yml
        type: AsyncAPI
    description: >-
      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.
common:
  - type: Portal
    url: https://www.regal.ai
  - type: Documentation
    url: https://developer.regal.ai
  - type: Documentation
    url: https://developer.regal.ai/docs
  - type: Documentation
    url: https://developer.regal.ai/reference/overview
  - type: GettingStarted
    url: https://developer.regal.ai/docs/plan-your-implementation
  - type: Documentation
    url: https://developer.regal.ai/llms.txt
  - type: FAQ
    url: https://developer.regal.ai/reference/faq
  - type: SupportPortal
    url: https://support.regal.ai/hc/en-us
  - type: Documentation
    url: https://support.regal.ai/hc/en-us/articles/5725458229531-Integration-Guides-API-Docs
  - type: Login
    url: https://app.regal.io
  - type: SignUp
    url: https://www.regal.ai/get-a-demo
  - type: Pricing
    url: https://www.regal.ai/pricing
  - type: Plans
    url: plans/regal-ai-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/regal-ai-rate-limits.yml
  - type: FinOps
    url: finops/regal-ai-finops.yml
  - type: Blog
    url: https://www.regal.ai/blog
  - type: ChangeLog
    url: https://www.regal.ai/blog/january-2025-releases
  - type: Customers
    url: https://www.regal.ai/customers
  - type: Product
    url: https://www.regal.ai/ai-agents
  - type: Product
    url: https://www.regal.ai/sales-dialer
  - type: Product
    url: https://www.regal.ai/journey-builder
  - type: Product
    url: https://www.regal.ai/conversation-intelligence
  - type: Careers
    url: https://www.regal.ai/careers
  - type: Company
    url: https://www.regal.ai/about
  - type: Contact
    url: https://www.regal.ai/contact
  - type: TrustCenter
    url: https://www.regal.ai/security
  - type: PrivacyPolicy
    url: https://www.regal.ai/privacy-policy
  - type: TermsOfService
    url: https://www.regal.ai/terms-of-service
  - type: LinkedIn
    url: https://www.linkedin.com/company/regal-ai-official
  - type: Twitter
    url: https://twitter.com/regalio
  - type: YouTube
    url: https://www.youtube.com/@regalio
  - type: Integrations
    url: https://developer.regal.ai/docs/salesforce
    name: Salesforce
  - type: Integrations
    url: https://developer.regal.ai/docs/hubspot
    name: HubSpot
  - type: Integrations
    url: https://developer.regal.ai/docs/segment
    name: Segment
  - type: Integrations
    url: https://developer.regal.ai/docs/mparticle
    name: mParticle
  - type: Integrations
    url: https://developer.regal.ai/docs/zendesk
    name: Zendesk
  - type: Integrations
    url: https://developer.regal.ai/docs/kustomer
    name: Kustomer
  - type: Integrations
    url: https://developer.regal.ai/docs/klaviyo
    name: Klaviyo
  - type: Integrations
    url: https://developer.regal.ai/docs/braze
    name: Braze
  - type: Integrations
    url: https://developer.regal.ai/docs/marketo
    name: Marketo
  - type: Integrations
    url: https://developer.regal.ai/docs/customerio
    name: Customer.io
  - type: Integrations
    url: https://developer.regal.ai/docs/iterable
    name: Iterable
  - type: Integrations
    url: https://developer.regal.ai/docs/microsoft-dynamics-365
    name: Microsoft Dynamics 365
  - type: Integrations
    url: https://developer.regal.ai/docs/zoho
    name: Zoho
  - type: Integrations
    url: https://developer.regal.ai/docs/hightouch
    name: Hightouch
  - type: Integrations
    url: https://developer.regal.ai/docs/calcom
    name: Cal.com
  - type: Integrations
    url: https://developer.regal.ai/docs/calendly
    name: Calendly
  - type: Integrations
    url: https://developer.regal.ai/docs/zapier
    name: Zapier
  - type: Integrations
    url: https://developer.regal.ai/docs/sendgrid
    name: SendGrid
  - type: Integrations
    url: https://developer.regal.ai/docs/slack
    name: Slack
  - type: Integrations
    url: https://developer.regal.ai/docs/microsoft-teams
    name: Microsoft Teams
  - type: Integrations
    url: https://developer.regal.ai/docs/8x8
    name: 8x8
  - type: Integrations
    url: https://developer.regal.ai/docs/five9
    name: Five9
  - type: Integrations
    url: https://developer.regal.ai/docs/talkdesk
    name: Talkdesk
  - type: Integrations
    url: https://developer.regal.ai/docs/snowflake-data-share
    name: Snowflake Data Share
  - type: Integrations
    url: https://developer.regal.ai/docs/amazon-s3
    name: Amazon S3
  - type: Integrations
    url: https://developer.regal.ai/docs/freshdesk
    name: Freshdesk
  - type: Integrations
    url: https://developer.regal.ai/docs/assembled
    name: Assembled
  - type: Integrations
    url: https://developer.regal.ai/docs/gong
    name: Gong
  - type: Integrations
    url: https://developer.regal.ai/docs/balto
    name: Balto
  - type: Integrations
    url: https://developer.regal.ai/docs/kindlyai
    name: Kindly
  - type: Embed
    url: https://developer.regal.ai/docs/salesforce-embed
    name: Salesforce Embed
  - type: Embed
    url: https://developer.regal.ai/docs/kustomer-embed
    name: Kustomer Embed
  - type: Embed
    url: https://developer.regal.ai/docs/retool
    name: Retool Embed
  - type: Embed
    url: https://developer.regal.ai/docs/chrome-extension
    name: Chrome Extension
  - type: SingleSignOn
    url: https://developer.regal.ai/docs/google-sso
    name: Google SSO
  - type: SingleSignOn
    url: https://developer.regal.ai/docs/okta-sso
    name: Okta SSO
  - type: SingleSignOn
    url: https://developer.regal.ai/docs/azure-sso
    name: Azure SSO
  - type: SCIM
    url: https://developer.regal.ai/docs/okta-scim
    name: Okta SCIM
  - type: Vocabulary
    url: vocabulary/regal-ai-vocabulary.yml
  - type: Features
    data:
      - AI Phone Agents for 24/7 inbound and outbound voice with sub-second latency and 30+ languages
      - SMS, Chat, and WebRTC AI Agents sharing the same prompt, knowledge base, and action library
      - No-code Agent Builder with prompts, dynamic variables, actions, action sequences, branching, and agent variants
      - >-
        Custom Actions framework that lets voice agents POST structured payloads to customer HTTP endpoints and branch
        on the response
      - >-
        Journey Builder for multi-channel customer journeys including triggered outbound calls gated by TCPA opt-in
        flags
      - >-
        Conversation Intelligence with AI call analysis, custom AI analysis and reporting, coverage gap dashboard, and
        cross-transcript search
      - >-
        Sales Dialer with batch dialing, outbound routing, branded caller ID, spam remediation, and iOS call screening
        handling
      - Copilot for AI-assisted agent design and tuning
      - >-
        Single Custom Events ingestion endpoint (events.regalvoice.com/events) with userId/phone/email identity
        resolution at 300 RPS
      - >-
        v1 Management API for Business Profiles, Active Phone Numbers, Campaigns, Dispositions, Branded Phone Numbers,
        and SMS sending
      - >-
        40+ reporting webhook event types covering calls, SMS, MMS, email, voicemail, contact lifecycle, scheduling, and
        custom tasks
      - >-
        Native data integrations with Segment, mParticle, HubSpot, Salesforce, Zendesk, Kustomer, Klaviyo, Braze,
        Marketo, Customer.io, Iterable, Microsoft Dynamics 365, Zoho, Hightouch, Cal.com, Calendly, Snowflake Data
        Share, Amazon S3, Slack, Microsoft Teams, SendGrid, Zapier
      - CCaaS integrations with 8x8, Five9, and Talkdesk
      - Embeddable iframe for Salesforce, Kustomer, Retool, and Chrome Extension
      - SSO via Google, Okta, and Azure; SCIM via Okta
      - SOC 2, HIPAA, GDPR, CCPA, and DPA compliance with no customer data used for LLM training
    sources:
      - https://www.regal.ai
      - https://developer.regal.ai
      - https://developer.regal.ai/reference/overview
      - https://developer.regal.ai/docs/reporting-webhooks
      - https://www.regal.ai/blog/january-2025-releases
    updated: '2026-05-24'
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com
    url: https://apievangelist.com