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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Alianza

Alianza Telephone Number API

The Telephone Number API from Alianza — 28 operation(s) for telephone number.

Documentation Provider Profile APIs.io OpenAPI GitHub

Alianza Telephone Number API is one of 60 APIs that Alianza publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Telephone Number. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 37 operations across 28 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against 4 base URLs: https://api.d2.alianza.com, https://api.q2.alianza.com, https://api.b2.alianza.com, https://api.alianza.com.

37 operations 28 paths 27 schemas 3 DELETE17 GET1 PATCH9 POST7 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://api.alianza.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Alianza Telephone Number API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-AUTH-TOKEN (X-Auth-Token).

Paths & Operations 37

Across 28 paths, the API surfaces 37 operations — 3 DELETE, 17 GET, 1 PATCH, 9 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Telephone Number 37
GET
/v2/partition/{partitionId}/telephonenumber
retrieve_5 2 params → 200
POST
/v2/partition/{partitionId}/telephonenumber
Create telephone number
createTelephoneNumber 2 params body → 200400404
GET
/v2/partition/{partitionId}/telephonenumber/{tn}
Retrieve telephone number
retrieveTelephoneNumber 3 params → 200400404
DELETE
/v2/partition/{partitionId}/telephonenumber/{tn}
Delete telephone number
delete_2 3 params → 200400404
GET
/v2/partition/{partitionId}/telephonenumber/search
Telephone number search
search_1 8 params → 200400404
GET
/v2/partition/{partitionId}/telephonenumber/{tn}/availability
Retrieve telephone number availability
retrieveTelephoneNumberAvailability 3 params → 200
POST
/v2/partition/{partitionId}/telephonenumber/bulkimportdeprecated
Bulk telephone number import
bulkInsert 2 params body → 200400404
POST
/v2/partition/{partitionId}/telephonenumber/bulkimport_2
Bulk telephone number import
bulkInsert2 2 params body → 200202
GET
/v2/partition/{partitionId}/telephonenumber/exportstatussearch
Export as CSV telephone number status search
exportStatusSearch 10 params → 400404
GET
/v2/partition/{partitionId}/telephonenumber/exportstatussearch_2
Export as CSV telephone number status search
exportStatusSearch2 10 params → 200202400404
PUT
/v2/partition/{partitionId}/telephonenumber/{tn}/cooldown/recover
Delete telephone number cooldown
cooldownRecover 3 params → 200400404
PUT
/v2/partition/{partitionId}/telephonenumber/{tn}/reserve
Reserve a telephone number
reserve 3 params → 200400404
DELETE
/v2/partition/{partitionId}/telephonenumber/{tn}/reserve
Delete a reserve on telephone number
releaseReservation 3 params → 200400404
GET
/v2/partition/{partitionId}/telephonenumber/statussearch
Telephone number status search
statusSearch 11 params → 200400404
GET
/v2/partition/{partitionId}/telephonenumber/{tn}/fmfmcheck
isTnOffNet 3 params → 200
GET
/v2/partition/{partitionId}/telephonenumber/export
getInventoryPlan 2 params → 200
GET
/v2/partition/{partitionId}/telephonenumber/export_2
Export telephone numbers as csv
getInventoryPlan2 2 params → 200202
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}
Retrieve a telephone number on an account
retrieveTelephoneNumberOnAccount 4 params → 200400404
PUT
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}
Update telephone number on an account
updateTelephoneNumberOnAccount 4 params body → 200400404
DELETE
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}
Delete telephone number on an account
deleteTelephoneNumberOnAccount 4 params → 400404
PATCH
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}
Update telephone number on an account
patchTelephoneNumberOnAccount 4 params body → 200400404
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber
Retrieve all telephone numbers on an account
retrieveAccountTelephoneNumbers 4 params → 200400404
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber
Create a telephone number or add telephone number to an account
createOrAddTelephoneNumberToAccount 3 params body → 200400404
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/groupid/{groupId}
Retrieve all telephone number for end users
retrieveTelephoneNumbersByUserGroups 4 params → 200400404
PUT
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}/911-address/original/accept
Accept original E911 address
acceptOriginalE911 6 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests
Get all unfinished or archived activations with dynamic inventory
retrieveDynamicInventoryActivations 5 params → 200400
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests
Activate a tn that will be requested dynamically from carrier. TN is not known at the moment of initiating of activation
createOrAddTelephoneNumberToAccountWithDynamicInventory 3 params body → 200400404
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests/{orderId}
Get activation with dynamic inventory regardless of status
getDynamicInventoryActivation 4 params → 200400404
PUT
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests/{orderId}
Updates dynamic reservation object
updateTelephoneNumberToAccountWithDynamicInventory 4 params body → 200400404
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests/actions/cancel
Cancel and remove reservation object
cancelAndRemoveDynamicInventoryReservation 3 params body → 400
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests/actions/resubmit
Revise and resubmit dynamic reservation object
reviseAndResubmitDynamicInventoryReservation 3 params body → 200400404
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/tn-requests/{orderId}/refresh
Refresh dynamic activation status
refreshDynamicInventoryActivation 4 params → 404
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}/911-address/usages
Retrieve a telephone number usages on an account
retrieveTelephoneNumberUsages 4 params → 200400404
GET
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}/911-address/correction
Get adjusted E911 address
getE911Correction 4 params → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}/911-address/correction/accept
Accept adjusted E911 address
acceptE911Correction 4 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/external
Create or updates already activated telephone number to an account
createOrUpdateExternalTelephoneNumberToAccount 3 params body → 200400404
PUT
/v2/partition/{partitionId}/account/{accountId}/telephonenumber/{tn}/destination
destination 4 params body → 200

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are PortX (26 properties), ServiceActivationEventX (24 properties), LatLongCustomerServiceRecordX (23 properties), TelephoneNumberAccountV2X (22 properties). Each schema is shown below with its type and property counts.

E911AddressX
object
21 properties
TelephoneNumberViewX
object
21 properties
ServiceActivationEventLogX
object
6 properties
LatLongCustomerServiceRecordX
object
23 properties
TelephoneNumberAvailabilityX
object
13 properties
ServiceActivationEventResponseX
object
2 properties
CustomerServiceRecordX
object
21 properties
MultipartFormDataInput
object
TelephoneNumberReservedX
object
4 properties
Job
object
9 properties
JobUploadKey
object
1 property
TelephoneNumberDestinationX
object
8 properties
DynamicTelephoneNumberActivationX
object
15 properties
L3SettingsX
object
6 properties
CancelActionX
object
3 properties
AddressX
object
17 properties
ExternalTnX
object
11 properties
TelephoneNumberUsagesX
object
4 properties
TelecomSettingsX
object
8 properties
TelephoneNumberActivationsV2X
object
11 properties
TelephoneNumberAccountV2X
object
22 properties
DirectoryListingX
object
3 properties
JobError
object
4 properties
PortX
object
26 properties
TelephoneNumberAccountBareX
object
10 properties
ServiceActivationEventX
object
24 properties
TnData
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alianza-telephone-number-api-openapi.yml Raw ↑

Other APIs Alianza publishes across the network.

Alianza Account API
AE Profile APIs.io
Alianza Account Device API
AE Profile APIs.io
Alianza Account Device Line API
AE Profile APIs.io
Alianza Account Prevalidate API
AE Profile APIs.io
Alianza Account User API
AE Profile APIs.io
Alianza Address API
AE Profile APIs.io
Alianza Asynchronous JOB Tracker API
AE Profile APIs.io
Alianza Authorize API
AE Profile APIs.io
Alianza Brand Settings API
AE Profile APIs.io
Alianza Bulk Operation Collection API
AE Profile APIs.io
Alianza Bulk Operation Job API
AE Profile APIs.io
Alianza Business Line API
AE Profile APIs.io
#Telephone Number
← Back to A APIs
API Details
ID
alianza:alianza-telephone-number-api
Base URL
https://api.alianza.com
Docs
https://developer.alianza.com/provisioning-api
Provider
Alianza
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=alianza-telephone-number-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/alianza-telephone-number-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Alianza Telephone Number 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.