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 Devices API

The devices API from Wazo — 16 operation(s) for devices.

Documentation Provider Profile APIs.io OpenAPI GitHub

Wazo Devices 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 Devices. 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 24 operations across 16 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /1.1, /api/provd/0.2.

24 operations 16 paths 16 schemas 4 DELETE11 GET5 POST4 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 Devices 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 24

Across 16 paths, the API surfaces 24 operations — 4 DELETE, 11 GET, 5 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

devices 24
GET
/devices
List devices
list_devices 7 params → 200400
POST
/devices
Create device
create_device 1 param body → 201400
GET
/devices/{device_id}
Get device
get_device 2 params → 200404
PUT
/devices/{device_id}
Update device
update_device 2 params body → 204400404
DELETE
/devices/{device_id}
Delete device
delete_device 2 params → 204400404
GET
/devices/{device_id}/autoprov
Reset device to autoprov
reset_device_autoprov 2 params → 204400404
GET
/devices/{device_id}/synchronize
Synchronize device
synchronize_device 2 params → 204400404
GET
/devices/unallocated
List unallocated devices
list_unallocated_devices 5 params → 200400
PUT
/devices/unallocated/{device_id}
Assign unallocated device tenant
assign_unallocated_device_tenant 2 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
GET
/dev_mgr
Get the Device Manager resource
→ 200
GET
/dev_mgr/devices
List and find devices
7 params → 200
POST
/dev_mgr/devices
Create a device
1 param body → 201400415
GET
/dev_mgr/devices/{device_id}
Get a device by ID
2 params → 200404
PUT
/dev_mgr/devices/{device_id}
Update a device
2 params body → 204404415500
DELETE
/dev_mgr/devices/{device_id}
Delete a device
2 params → 204404
POST
/dev_mgr/synchronize
Synchronize a device
2 params → 201415
GET
/dev_mgr/synchronize/{operation_id}
Get the status of a synchronize Operation In Progress
1 param → 200404
DELETE
/dev_mgr/synchronize/{operation_id}
Delete the Operation In Progress
1 param → 204404
POST
/dev_mgr/reconfigure
Reconfigure a device
2 params → 204400
POST
/dev_mgr/dhcpinfo
Push DHCP request information
2 params → 204

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Device_2 (14 properties), Device (14 properties), DHCPInfo (4 properties), LinkObject (2 properties). Each schema is shown below with its type and property counts.

DeviceItems
object
2 properties 1 required
DeviceOptions
object
List of standard keys
1 property
LineDeviceItems
object
2 properties 1 required
LineDevice
object
2 properties
Error
array
Device
object
14 properties
DevicesList
object
A list of devices
1 property
IdObject
object
1 property
DeviceObject
object
A device object
1 property
DHCPInfo
object
4 properties
ErrorMessage
string
Error message response
LinksObject
object
Links object
1 property
OperationInProgressObject
object
1 property
DHCPInfoObject
object
1 property
LinkObject
object
Link Object
2 properties
Device_2
object
A device schema
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-devices-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
#Devices
← Back to W APIs
API Details
ID
wazo:wazo-devices-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-devices-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/wazo-devices-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 Devices 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.