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

The incalls API from Wazo — 4 operation(s) for incalls.

Documentation Provider Profile APIs.io OpenAPI GitHub

Wazo Incalls 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 incalls. 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 9 operations across 4 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against a single base URL, /1.1.

9 operations 4 paths 34 schemas 3 DELETE2 GET1 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Wazo Incalls 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 9

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

incalls 9
GET
/incalls
List incoming calls
list_incalls 8 params → 200
POST
/incalls
Create incoming call
create_incall 1 param body → 201400
GET
/incalls/{incall_id}
Get incoming call
get_incall 2 params → 200404
PUT
/incalls/{incall_id}
Update incoming call
update_incall 2 params body → 204400404
DELETE
/incalls/{incall_id}
Delete incoming call
delete_incall 2 params → 204400404
PUT
/incalls/{incall_id}/extensions/{extension_id}
Associate incall and extension
associate_incall_extension 2 params → 204400404
DELETE
/incalls/{incall_id}/extensions/{extension_id}
Dissociate incall and extension
dissociate_incall_extension 2 params → 204400404
PUT
/incalls/{incall_id}/schedules/{schedule_id}
Associate incall and schedule
associate_incall_schedule 3 params → 204400404
DELETE
/incalls/{incall_id}/schedules/{schedule_id}
Dissociate incall and schedule
dissociate_incall_schedule 3 params → 204400404

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are DestinationType (14 properties), DestinationApplicationApplication (6 properties), DestinationQueue (5 properties), DestinationUser (4 properties). Each schema is shown below with its type and property counts.

DestinationApplicationDISA
DestinationApplicationDirectory
DestinationUser
object
4 properties 2 required
DestinationOutcall
object
3 properties 3 required
DestinationHangup
object
1 property 1 required
DestinationQueue
object
5 properties 2 required
DestinationConference
object
2 properties 2 required
DestinationGroup
object
3 properties 2 required
DestinationHangupNormal
1 required
DestinationApplicationVoicemail
DestinationHangupBusy
1 required
DestinationHangupCause
object
3 properties
DestinationApplication
object
1 property 1 required
DestinationType
object
14 properties
IncallRelationExtensions
object
1 property
DestinationCustom
object
2 properties 2 required
DestinationIVR
object
2 properties 2 required
IncallRelationSchedules
object
1 property
ExtensionRelationBase
object
3 properties
DestinationSound
object
4 properties 2 required
Incall
DestinationHangupCongestion
1 required
DestinationApplicationCustom
2 required
DestinationVoicemail
object
4 properties 2 required
DestinationApplicationApplication
object
6 properties
DestinationSwitchboard
object
2 properties 2 required
ScheduleRelationBase
object
3 properties
DestinationApplicationCallbackDISA
DestinationApplicationFaxToMail
2 required
Error
array
IncallItems
object
2 properties 1 required
DestinationNone
object
1 property 1 required
IncallRelationBase
object
1 property
DestinationExtension
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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