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
Wazo

Wazo Lines API

The lines API from Wazo — 15 operation(s) for lines.

Documentation Provider Profile APIs.io OpenAPI GitHub

Wazo Lines API is one of 113 APIs that Wazo publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Lines. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, a changelog, authentication docs, and an AsyncAPI specification.

This API exposes 25 operations across 15 paths, and defines 55 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /1.0, /1.1.

25 operations 15 paths 55 schemas 8 DELETE6 GET2 POST9 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{wazo_stack}/api/auth/0.1
Authentication
API Key
Contact
Wazo Dev Team
Resource Areas
1

Authentication & Security 1

Wazo Lines API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (wazo_auth_token). By default, every request must be authenticated.

Paths & Operations 25

Across 15 paths, the API surfaces 25 operations — 8 DELETE, 6 GET, 2 POST, 9 PUT. Each is listed below with its method, path, parameters, and response codes.

lines 25
GET
/lines
List line endpoint statuses
1 param → 200503
POST
/lines
Create line
create_line 1 param body → 201400
GET
/lines/{line_id}
Get line
get_line 2 params → 200404
PUT
/lines/{line_id}
Update line
update_line 2 params body → 204400404
DELETE
/lines/{line_id}
Delete line
delete_line 2 params → 204404
PUT
/lines/{line_id}/applications/{application_uuid}
Associate line and application
associate_line_application 3 params → 204400404
DELETE
/lines/{line_id}/applications/{application_uuid}
Dissociate line and application
dissociate_line_application 3 params → 204400404
GET
/devices/{device_id}/lines
List lines associated to device
get_device_line_association 2 params → 200404
GET
/lines/{line_id}/devices
Get Device associated to Line
get_line_device 2 params → 200400404
PUT
/lines/{line_id}/devices/{device_id}
Associate line and device
associate_line_device 3 params → 204400404
DELETE
/lines/{line_id}/devices/{device_id}
Dissociate line and device
dissociate_line_device 3 params → 204400404
PUT
/lines/{line_id}/endpoints/custom/{custom_id}
Associate line and Custom endpoint
associate_line_endpoint_custom 2 params → 204400404
DELETE
/lines/{line_id}/endpoints/custom/{custom_id}
Dissociate line and Custom endpoint
dissociate_line_endpoint_custom 2 params → 204400404
PUT
/lines/{line_id}/endpoints/sccp/{sccp_id}
Associate line and SCCP endpoint
associate_line_endpoint_sccp 2 params → 204400404
DELETE
/lines/{line_id}/endpoints/sccp/{sccp_id}
Dissociate line and SCCP endpoint
dissociate_line_endpoint_sccp 2 params → 204400404
PUT
/lines/{line_id}/endpoints/sip/{sip_uuid}
Associate line and SIP endpoint
associate_line_endpoint_sip 2 params → 204400404
DELETE
/lines/{line_id}/endpoints/sip/{sip_uuid}
Dissociate line and SIP endpoint
dissociate_line_endpoint_sip 2 params → 204400404
DELETE
/lines/{line_id}/extensions/{extension_id}
Dissociate line and extension
dissociate_line_extension 2 params → 204400404
PUT
/lines/{line_id}/extensions/{extension_id}
Associate line and extension
associate_line_extension 2 params → 204400404
POST
/lines/{line_id}/extensions
Create extension
create_line_extension 2 params body → 201400404
DELETE
/users/{user_id}/lines/{line_id}
Dissociate user and line
dissociate_user_line 2 params → 204400404
PUT
/users/{user_id}/lines/{line_id}
Associate user and line
associate_user_line 2 params → 204400404
PUT
/users/{user_id}/lines
Associate user and lines
associate_user_lines 1 param body → 204400404
GET
/users/{user_uuid}/lines/{line_id}/associated/endpoints/sip
Get SIP endpoint of a line for a user
get_user_line_associated_endpoints_sip 3 params → 200400
GET
/users/{user_uuid}/lines/main/associated/endpoints/sip
Get SIP endpoint of main line for a user
get_user_line_main_associated_endpoints_sip 2 params → 200400

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are EndpointSIP (14 properties), Line (7 properties), EndpointLine (5 properties), EndpointSipRelationBase (4 properties). Each schema is shown below with its type and property counts.

EndpointLines
object
3 properties
EndpointLine
object
5 properties
Error
object
Error message for the client
4 properties
SIPTransportRelation
object
1 property 1 required
ExtensionRelationConference
object
1 property
LineRelationEndpoints
object
3 properties
EndpointSIP
object
14 properties
LineEndpointSIP
object
1 property
ExtensionRelationLines
object
1 property
EndpointRelationLine
object
1 property
SIPAuthSectionOptions
ParkingLotRelationBase
object
2 properties
ExtensionRelationParkingLot
object
1 property
LineRelationExtensions
object
1 property
Extension
LineRelationApplication
object
1 property
ExtensionRelationOutcall
object
1 property
KeyValueOption
array
Options must have the following form: { "options": [ ["option", "value"], ] }
EndpointSccpRelationBase
object
1 property
LineEndpointSCCP
object
1 property
ExtensionRelationQueue
object
1 property
ExtensionRelationGroup
object
1 property
LineID
object
1 property
ApplicationRelationBase
object
2 properties
EndpointSipRelationBase
object
4 properties
EndpointSIPTemplatesRelation
object
2 properties 1 required
ConferenceRelationBase
object
2 properties
QueueRelationBase
object
3 properties
OutcallRelationBase
object
2 properties
EndpointCustomRelationBase
object
2 properties
Line
object
7 properties 1 required
LineItems
object
2 properties 1 required
ExtensionRelationBase
object
3 properties
LineEndpointCustom
object
1 property
LineDeviceItems
object
2 properties 1 required
LineCreate
TrunkRelationBase
object
2 properties
LineExtensions
object
1 property
LineRelationUsers
object
1 property
EndpointCustom
SIPAORSectionOptions
SIPRegistrationSectionOptions
LinesID
object
1 property
SIPEndpointSectionOptions
ExtensionRelationIncall
object
1 property
EndpointSccp
GroupRelationBase
object
3 properties
LineDevice
object
2 properties
LineView
Error_2
array
EndpointRelationTrunk
object
1 property
LineRelationBase
object
2 properties
UserRelationBase
object
3 properties
SIPIdentifySectionOptions
IncallRelationBase
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-lines-api-openapi.yml Raw ↑

Other APIs Wazo publishes across the network.

Wazo Phone Provisioning API (wazo-provd)
AE Profile APIs.io
Wazo Websocket Event Stream (wazo-websocketd)
AE Profile APIs.io
Wazo Aastra API
AE Profile APIs.io
Wazo Access Features API
AE Profile APIs.io
Wazo Action API
AE Profile APIs.io
Wazo Adhoc Conferences API
AE Profile APIs.io
Wazo Admin API
AE Profile APIs.io
Wazo Agent Statistics API
AE Profile APIs.io
Wazo Agents API
AE Profile APIs.io
Wazo Applications API
AE Profile APIs.io
Wazo Asterisk API
AE Profile APIs.io
Wazo Backends API
AE Profile APIs.io
#Lines
← Back to W APIs
API Details
ID
wazo:wazo-lines-api
Base URL
https://{wazo_stack}/api/auth/0.1
Docs
https://api.wazo.io/documentation/api/authentication.html
Provider
Wazo
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=wazo-lines-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/wazo-lines-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 Wazo Lines 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.