How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Regal Branded Phone Numbers API

Carrier-level branded caller ID and spam remediation

Regal Branded Phone Numbers API is one of 10 APIs that Regal publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Branded Phone Numbers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, a changelog, and 4 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.regal.ai/v1.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.regal.ai/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Regal Branded Phone Numbers API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Branded Phone Numbers 4

Carrier-level branded caller ID and spam remediation

GET
/brandedPhoneNumbers
List Branded Phone Numbers
listBrandedPhoneNumbers 10 params → 200400401403429
POST
/brandedPhoneNumbers
Post Branded Phone Number
postBrandedPhoneNumber body → 201400403409429
PATCH
/brandedPhoneNumbers/{phoneNumber}
Patch Branded Phone Number
patchBrandedPhoneNumber 1 param body → 200400403404429
DELETE
/brandedPhoneNumbers/{phoneNumber}
Delete Branded Phone Number
deleteBrandedPhoneNumber 1 param → 200400403404429

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are BrandedPhoneNumber (7 properties), BrandedPhoneNumberCreate (7 properties), BrandedPhoneNumberPatch (6 properties), CarrierFeature (4 properties). Each schema is shown below with its type and property counts.

BrandedPhoneNumberCreate
object
7 properties 3 required
BrandedPhoneNumberPatch
object
6 properties
BrandedPhoneNumber
object
7 properties
CarrierFeature
object
4 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

regal-ai-branded-phone-numbers-api-openapi.yml Raw ↑

Other APIs Regal publishes across the network.

Regal Reporting Webhooks
Regal Business Profiles API
Regal Campaigns API
Regal Dispositions API
Regal Events API
Regal Messages API
Regal Phone Numbers API
Regal Users API
Regal Call Handoffs API
Where this information came from

This is an independent, third-party profile of Regal Branded Phone Numbers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.