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

Alianza Business Line API

The Business Line API from Alianza — 22 operation(s) for business line.

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

Tagged areas include Business Line. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 35 operations across 22 paths, and defines 19 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.

35 operations 22 paths 19 schemas 5 DELETE17 GET7 POST6 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 Business Line 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 35

Across 22 paths, the API surfaces 35 operations — 5 DELETE, 17 GET, 7 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Business Line 35
GET
/v2/partition/{partitionId}/account/{accountId}/business-line
Retrieve business line list
retrieveBusinessLines 3 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line
Create a new business line
createBusinessLine 3 params body → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/views/expanded
Retrieve business line list with lines in expanded view format
retrieveBusinessLinesExpanded 3 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/call-handling
Retrieve business line call handling
getBusinessLineCallHandling 4 params → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/call-handling
Update business line call handling
putBusinessLineCallHandling 4 params body → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}
Retrieve business line
retrieveBusinessLine 4 params → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}
Update business line
updateBusinessLine 4 params body → 200
DELETE
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}
Delete business line
deleteBusinessLine 4 params → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/views/expanded
Retrieve business line in expanded view format
retrieveBusinessLineExpanded 4 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/registration
Retrieve registration status for business line
businessLineRegistrationStatus 4 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment/rpc/swap
Swap business line port assignment(s)
swapBusinessLinePortAssignment 4 params body → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment
Retrieve business line port assignment
getBusinessLinePortAssignment 4 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment
Create business line port assignment
createBusinessLinePortAssignment 4 params body → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment
Update business line port assignment
updateBusinessLinePortAssignment 4 params body → 200
DELETE
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment
Delete business line port assignment
deleteBusinessLinePortAssignment 4 params → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/port-assignment/push-provisioning-logs
Retrieve provisioning logs from third party notifications
getPushProvisioningLogs 4 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/sip-credentials
Retrieve SIP credentials
getBusinessLineSipCredentials 4 params → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/sip-credentials
Update SIP credentials
putBusinessLineSipCredentials 4 params body → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/{businessLineId}/sip-credentials/username-availability-check/{username}
SIP Username Availability Check
isUsernameAvailable 5 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box
Retrieve all business line voicemail boxes on this account
retrieveBusinessLineVoicemailBoxes 3 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box
Create business line voicemail box on account
createBusinessLineVoicemailBox 3 params body → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/views/expanded
Retrieve all business line voicemail boxes on this account including references
retrieveBusinessLineVoicemailBoxesExpandedView 3 params → 200
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}
Retrieve business line voicemail box
retrieveBusinessLineVoicemailBox 4 params → 200
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}
Update business line voicemail box
updateBusinessLineVoicemailBox 4 params body → 200
DELETE
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}
Delete business line voicemail box
deleteBusinessLineVoicemailBox 4 params → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/views/expanded
Retrieve business line voicemail box including references
retrieveBusinessLineVoicemailBoxExpandedView 4 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/rpc/check-pin-status
Check business line voicemail box PIN status
checkBusinessLineVoicemailBoxPinStatus 4 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/rpc/reset-pin
Reset the PIN for a business line voicemail box
resetBusinessLineVoicemailBoxPinStatus 4 params → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message/{messageId}
Retrieve a business line voicemail message
retrieveBusinessLineVoicemailMessage 5 params → 200
DELETE
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message/{messageId}
Delete a business line voicemail message
deleteBusinessLineVoicemailMessage 5 params → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message
Retrieve business line voicemail messages
retrieveBusinessLineVoicemailMessages 4 params → 200
DELETE
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message
Delete business line voicemail messages
deleteBusinessLineVoicemailMessages 4 params → default
PUT
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message/bulk-update
Bulk update of voicemail messages
bulkVoicemailMessageUpdate 4 params body → default
GET
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message/{messageId}/media
Retrieve a business line voicemail message media
retrieveBusinessLineVoicemailMessageMedia 5 params → 200
POST
/v2/partition/{partitionId}/account/{accountId}/business-line/voicemail-box/{voicemailBoxId}/message/{messageId}/set-read-status
Update business line voicemail message read flag
updateBusinessLineVoicemailMessageRead 5 params body → default

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are BusinessLineExpandedView (10 properties), VoicemailMessage (10 properties), VoicemailBoxExpandedView (9 properties), VoicemailBox (8 properties). Each schema is shown below with its type and property counts.

PortAssignment
object
5 properties 1 required
PortAssignmentView
object
4 properties
VoicemailBoxExpandedView
object
9 properties
RingFailoverAction
object
1 property 1 required
BusinessLineExpandedView
object
10 properties
SipCredentials
object
2 properties 2 required
VoicemailMessage
object
10 properties
VoicemailBoxAssignment
object
2 properties
PinStatusResponse
object
1 property
VoicemailBox
object
8 properties 3 required
SipCredentialsView
object
1 property
RegistrationStatus
object
2 properties
CallHandling
object
7 properties 4 required
RingTimeoutConfiguration
object
1 property 1 required
CallHandlingView
object
7 properties
BusinessLine
object
7 properties 3 required
DeviceSwap
object
2 properties 2 required
BulkVoicemailAction
object
2 properties 1 required
ReadMessage
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alianza-business-line-api-openapi.yml Raw ↑

Other APIs Alianza publishes across the network.

Alianza Account API
Alianza Account Device API
Alianza Account Device Line API
Alianza Account Prevalidate API
Alianza Account User API
Alianza Address API
Alianza Asynchronous JOB Tracker API
Alianza Authorize API
Alianza Brand Settings API
Alianza Bulk Operation Collection API
Alianza Bulk Operation Job API
Alianza Business Line Hunt Group API
Where this information came from

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