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

Relevance AI Analytics API

The analytics API from Relevance AI — 23 operation(s) for analytics.

Relevance AI Analytics API is one of 32 APIs that Relevance AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Analytics. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 23 operations across 23 paths, and defines 40 schemas. It is described by OpenAPI 3.2.0, at version latest.

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

23 operations 23 paths 40 schemas 6 GET17 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://api-{region}.stack.tryrelevance.com/latest
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Relevance AI Analytics API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AuthorizationHeader). By default, every request must be authenticated.

  • AuthorizationHeader — Authorization credentials. Header authorization should be in the form of: project:apikey

Paths & Operations 23

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

Analytics 23
POST
/analytics/get_metrics
GetMetrics
GetMetrics body → 200
POST
/analytics/get_agent_breakdown
GetAgentBreakdown
GetAgentBreakdown body → 200
POST
/analytics/get_action_breakdown
GetActionBreakdown
GetActionBreakdown body → 200
POST
/analytics/get_workforce_breakdown
GetWorkforceBreakdown
GetWorkforceBreakdown body → 200
POST
/analytics/get_agent_llm_usage_by_model
GetAgentModelBreakdown
GetAgentModelBreakdown body → 200
POST
/analytics/get_agent_errors
GetAgentErrors
GetAgentErrors body → 200
GET
/analytics/get_error_time_series
GetErrorTimeSeries
GetErrorTimeSeries 8 params → 200
GET
/analytics/get_task_timeline
GetTaskTimeline
GetTaskTimeline 5 params → 200
GET
/organizations/{organization_id}/analytics/concurrency_time_series
GetConcurrencyTimeSeriesByOrgId
GetConcurrencyTimeSeriesByOrgId 10 params → 200
GET
/organizations/{organization_id}/analytics/live_jobs
GetLiveJobsByOrgId
GetLiveJobsByOrgId 7 params → 200
GET
/task_ops/tab_counts
GetTaskOpsTabCounts
GetTaskOpsTabCounts → 200
GET
/analytics/get_usage
GetUsage
GetUsage 4 params → 200
POST
/analytics/tool/breakdown
GetToolUsageBreakdown
GetToolUsageBreakdown body → 200
POST
/analytics/tool/breakdown/timeseries
GetToolUsageBreakdownTimeseries
GetToolUsageBreakdownTimeseries body → 200
POST
/analytics/tool/timeseries
GetToolUsageTimeseries
GetToolUsageTimeseries body → 200
POST
/analytics/agent/breakdown
GetAgentUsageBreakdown
GetAgentUsageBreakdown body → 200
POST
/analytics/agent/breakdown/timeseries
GetAgentUsageBreakdownTimeseries
GetAgentUsageBreakdownTimeseries body → 200
POST
/analytics/agent/timeseries
GetAgentUsageTimeseries
GetAgentUsageTimeseries body → 200
POST
/analytics/workforce/breakdown
GetWorkforceUsageBreakdown
GetWorkforceUsageBreakdown body → 200
POST
/analytics/workforce/breakdown/timeseries
GetWorkforceUsageBreakdownTimeseries
GetWorkforceUsageBreakdownTimeseries body → 200
POST
/analytics/workforce/timeseries
GetWorkforceUsageTimeseries
GetWorkforceUsageTimeseries body → 200
POST
/analytics/project/timeseries
GetProjectUsageTimeseries
GetProjectUsageTimeseries body → 200
POST
/analytics/model/breakdown
GetModelUsageBreakdown
GetModelUsageBreakdown body → 200

Schemas 40

The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are GetMetricsInput (5 properties), GetAgentErrorsInput (5 properties), GetActionBreakdownInput (4 properties), GetAgentUsageBreakdownTimeseriesOutput (4 properties). Each schema is shown below with its type and property counts.

GetTaskTimelineOutput
object
1 property 1 required
GetLiveJobsByOrgIdOutput
object
2 properties 2 required
GetToolUsageBreakdownInput
object
3 properties 2 required
GetAgentUsageTimeseriesInput
object
3 properties 2 required
GetMetricsInput
object
5 properties 3 required
GetWorkforceUsageTimeseriesOutput
object
3 properties 3 required
GetErrorTimeSeriesOutput
object
4 properties 2 required
GetAgentUsageBreakdownInput
object
4 properties 2 required
GetMetricsOutput
object
3 properties 3 required
GetAgentUsageBreakdownTimeseriesInput
object
4 properties 2 required
GetWorkforceBreakdownInput
object
4 properties 2 required
GetAgentUsageTimeseriesOutput
object
3 properties 3 required
GetModelUsageBreakdownInput
object
4 properties 2 required
GetWorkforceUsageBreakdownInput
object
4 properties 2 required
GetToolUsageTimeseriesOutput
object
3 properties 3 required
GetToolUsageBreakdownOutput
object
3 properties 3 required
GetWorkforceUsageBreakdownTimeseriesOutput
object
4 properties 4 required
GetModelUsageBreakdownOutput
object
3 properties 3 required
GetProjectUsageTimeseriesInput
object
2 properties 2 required
GetWorkforceBreakdownOutput
object
1 property 1 required
GetToolUsageBreakdownTimeseriesInput
object
3 properties 2 required
GetWorkforceUsageBreakdownOutput
object
3 properties 3 required
GetAgentUsageBreakdownTimeseriesOutput
object
4 properties 4 required
GetActionBreakdownInput
object
4 properties 2 required
GetAgentBreakdownOutput
object
1 property 1 required
GetAgentErrorsOutput
object
3 properties 2 required
GetAgentModelBreakdownOutput
object
1 property 1 required
GetAgentModelBreakdownInput
object
3 properties 2 required
GetUsageOutput
object
2 properties 2 required
GetProjectUsageTimeseriesOutput
object
3 properties 3 required
GetActionBreakdownOutput
object
1 property 1 required
GetTaskOpsTabCountsOutput
object
4 properties 4 required
GetAgentBreakdownInput
object
3 properties 2 required
GetConcurrencyTimeSeriesByOrgIdOutput
object
3 properties 2 required
GetToolUsageTimeseriesInput
object
3 properties 2 required
GetWorkforceUsageBreakdownTimeseriesInput
object
4 properties 2 required
GetWorkforceUsageTimeseriesInput
object
3 properties 2 required
GetAgentUsageBreakdownOutput
object
3 properties 3 required
GetToolUsageBreakdownTimeseriesOutput
object
4 properties 4 required
GetAgentErrorsInput
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relevance-ai-analytics-api-openapi.yml Raw ↑

Other APIs Relevance AI publishes across the network.

Relevance AI MCP Server
Relevance AI Agent Debug Configs API
Relevance AI Agent Runtime Events API
Relevance AI Agents API
Relevance AI Alarms API
Relevance AI Apify API
Relevance AI Auth API
Relevance AI Billing API
Relevance AI Branding Kit API
Relevance AI Branding Kits API
Relevance AI Chat API
Relevance AI Evals API
Where this information came from

This is an independent, third-party profile of Relevance AI Analytics 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.