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

Wazo Backends API

The backends API from Wazo — 5 operation(s) for backends.

Wazo Backends 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 Backend. 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 10 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.1.

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

10 operations 5 paths 6 schemas 2 DELETE5 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1
Base URL
https://{wazo_stack}/api/auth/0.1
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Wazo Backends API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (wazo_auth_basic). An API key is passed in the header as X-Auth-Token (wazo_auth_token).

Paths & Operations 10

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

backends 10
GET
/backends
Retrieves the list of activated wazoauth.backends plugins
→ 200
GET
/backends/ldap
Get current tenant's LDAP backend configuration. If there is no configuration, all the fields will be null.
getLDAPBackendConfig 1 param → 200401
PUT
/backends/ldap
Update current tenant's LDAP backend configuration
updateLDAPBackendConfig 1 param body → 200401
DELETE
/backends/ldap
Delete current tenant's LDAP backend configuration
deleteLDAPBackendConfig 1 param → 204401
DELETE
/backends/saml
Delete current tenant's SAML backend configuration
deleteSAMLBackendConfig 1 param → 204401404500
GET
/backends/saml
Get current tenant's SAML backend configuration. If there is no configuration, all the fields will be null.
getSAMLBackendConfig 1 param → 200401500
POST
/backends/saml
Returns the created SAML configuration.
createSAMLBackendConfig 1 param body → 200401500
PUT
/backends/saml
Updates current tenant's SAML backend configuration
updateSAMLBackendConfig 1 param body → 200401500
GET
/backends/saml/metadata
Download the tenant's SAML metadata XML file.
1 param → 200401404500
GET
/backends/saml/acs_url_template
Get tenant's ACS URL template to use in the IDP configuration
→ 200401404500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are LDAPBackendConfig (10 properties), SAMLBackendConfig (3 properties), Error (3 properties), BackendList (1 property). Each schema is shown below with its type and property counts.

SAMLAcsUrlTemplate
object
1 property 1 required
BackendList
object
1 property
Error
object
3 properties
LDAPBackendConfig
object
10 properties 5 required
LDAPBackendConfigEdit
SAMLBackendConfig
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-backends-api-openapi.yml Raw ↑

Other APIs Wazo publishes across the network.

Wazo Phone Provisioning API (wazo-provd)
Wazo Websocket Event Stream (wazo-websocketd)
Wazo Aastra API
Wazo Access Features API
Wazo Action API
Wazo Adhoc Conferences API
Wazo Admin API
Wazo Agent Statistics API
Wazo Agents API
Wazo Applications API
Wazo Asterisk API
Wazo Blocklist API
Where this information came from

This is an independent, third-party profile of Wazo Backends 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.