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

Reporting-friendly exports (cursor pagination).

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

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

This API exposes 2 operations across 2 paths, and defines 6 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.

2 operations 2 paths 6 schemas 2 GET

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 Reporting 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 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Reporting 2

Reporting-friendly exports (cursor pagination).

GET
/api/v1/reporting/tenants/{tenantId}/assistant/conversations
List assistant conversations (reporting format)
listReportingBotConversations 6 params → 200400401403503
GET
/api/v1/reporting/tenants/{tenantId}/voc/conversations
List VOC conversations (reporting format)
listReportingVocConversations 6 params → 200400401403503

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are BotConversationRow (31 properties), VocConversationRow (30 properties), BotConversationReportingResponse (3 properties), VocConversationReportingResponse (3 properties). Each schema is shown below with its type and property counts.

VocConversationReportingResponse
object
3 properties 3 required
ReportingCursor
object
1 property 1 required
BotConversationRow
object
Reporting row for a assistant conversation. Keys are optimized for reporting/exports.
31 properties 9 required
VocConversationRow
object
Reporting row for a VOC conversation. Keys are optimized for reporting/exports.
30 properties
BotConversationReportingResponse
object
3 properties 3 required
ErrorResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

crescendo-reporting-api-openapi.yml Raw ↑

Other APIs Crescendo publishes across the network.

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

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