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

Crescendo Provisioning API

Tenant-scoped provisioning resources.

Crescendo Provisioning API is one of 5 APIs that Crescendo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 10 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.6.0.

Requests are made against a single base URL, https://platform.crescendo.ai.

10 operations 4 paths 4 schemas 4 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.6.0
Base URL
https://platform.crescendo.ai
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Crescendo Provisioning API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (API Key) (bearerAuth). An API key is passed in the query as bearer_token (bearerTokenQuery). By default, every request must be authenticated.

  • bearerTokenQuery — Alternative to the Authorization header. Prefer the Authorization header whenever possible.

Paths & Operations 10

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

Provisioning 10

Tenant-scoped provisioning resources.

GET
/api/v1/provisioning/tenants/{tenantId}
Get a provisioning document
getProvisioningTenant 1 param → 200400401403404
POST
/api/v1/provisioning/tenants/{tenantId}
Create or replace a provisioning document (POST = replace)
postProvisioningTenant 1 param body → 200201400401403
PUT
/api/v1/provisioning/tenants/{tenantId}
Update a provisioning document (PUT = merge update)
putProvisioningTenant 1 param body → 200400401403404
GET
/api/v1/provisioning/tenants/{tenantId}/{collection}
List a provisioning collection
listProvisioningCollection 2 params → 200400401403
GET
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}
Get a provisioning document by ID
getProvisioningDocument 3 params → 200400401403404
POST
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}
Create or replace a provisioning document (POST = replace)
postProvisioningDocument 3 params body → 200201400401403
PUT
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}
Update a provisioning document (PUT = merge update)
putProvisioningDocument 3 params body → 200400401403404
GET
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}/versions/current
Get the current version document
getProvisioningVersionCurrent 3 params → 200400401403404
POST
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}/versions/current
Create or replace the current version document (POST = replace)
postProvisioningVersionCurrent 3 params body → 200201400401403
PUT
/api/v1/provisioning/tenants/{tenantId}/{collection}/{docId}/versions/current
Update the current version document (PUT = merge update)
putProvisioningVersionCurrent 3 params body → 200400401403404

Schemas 4

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

ProvisioningCollectionEntry
object
2 properties 2 required
ProvisioningCollectionResponse
array
ProvisioningDocument
object
Arbitrary JSON object representing the provisioning resource.
ErrorResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

crescendo-provisioning-api-openapi.yml Raw ↑

Other APIs Crescendo publishes across the network.

Crescendo MCP API
Crescendo Reporting API
Crescendo Service API
Crescendo VOC API
Where this information came from

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