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

Dixa Analytics API

The Analytics API from Dixa — 5 operation(s) for analytics.

Dixa Analytics API is one of 20 APIs that Dixa 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, and rate-limit docs.

This API exposes 7 operations across 5 paths, and defines 46 schemas. It is described by OpenAPI 3.0.3, at version beta.

Requests are made against a single base URL, https://dev.dixa.io.

7 operations 5 paths 46 schemas 5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
beta
Base URL
https://dev.dixa.io/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 7

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

Analytics 7
GET
/beta/analytics/metrics
Metrics Catalogue
getAnalyticsMetrics 2 params → 200400500
POST
/beta/analytics/metrics
Get Metric Data
postAnalyticsMetrics body → 200400500
GET
/beta/analytics/metrics/{metricId}
Metric Description
getAnalyticsMetricsMetricid 1 param → 200400500
GET
/beta/analytics/filter/{filterAttribute}
Filter values
getAnalyticsFilterFilterattribute 3 params → 200400500
GET
/beta/analytics/records
Metric Records Catalogue
getAnalyticsRecords 2 params → 200400500
POST
/beta/analytics/records
Get Metric Records Data
postAnalyticsRecords 2 params body → 200400500
GET
/beta/analytics/records/{recordId}
Metric Record Description
getAnalyticsRecordsRecordid 1 param → 200400500

Schemas 46

The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are MetricMetadata (5 properties), MetricRecordMetadata (5 properties), GetMetricDataInputCsidFilter (5 properties), GetMetricDataInputPeriodFilter (5 properties). Each schema is shown below with its type and property counts.

FieldMetadata
object
3 properties 3 required
Filter
object
2 properties 1 required
GetMetricRecordsDataInputPeriodFilter
object
4 properties 3 required
PeriodFilter
GetMetricRecordsDataInputCsidFilter
object
4 properties 2 required
Field
object
2 properties 1 required
BooleanField
object
1 property 1 required
InstantField
object
1 property 1 required
GetMetricRecordsDataInput
PaginationLinks
object
2 properties
ServerError
object
1 property 1 required
BadRequest
object
1 property 1 required
MetricRecordMetadata
object
5 properties 2 required
GetMetricOutput
object
1 property 1 required
GetMetricsOutput
object
2 properties
PrimitiveField
DoubleAggregateValue
object
2 properties 2 required
DoubleField
object
1 property 1 required
AggregateMetadata
object
2 properties 1 required
FilterMetadata
object
2 properties 1 required
ListField
object
1 property
IntField
object
1 property 1 required
GetMetricRecordsOutput
object
2 properties
AggregateValue
GetMetricDataInput
MetricData
object
2 properties 1 required
Interval
object
2 properties 2 required
GetMetricDataInputCsidFilter
object
5 properties 2 required
AgentPresenceDurationValue
object
2 properties
MetricMetadata
object
5 properties 1 required
LongAggregateValue
object
2 properties 2 required
MetricRecord
object
3 properties 1 required
GetMetricDataOutput
object
1 property 1 required
PresenceDuration
object
2 properties 2 required
FieldType
LongField
object
1 property 1 required
FilterValue
object
2 properties 1 required
GetMetricRecordsDataOutput
object
2 properties
UUIDField
object
2 properties 1 required
GetMetricDataInputPeriodFilter
object
5 properties 3 required
StringField
object
2 properties 1 required
TimestampField
object
2 properties 2 required
Preset
object
1 property 1 required
GetFilterValuesOutput
object
2 properties
Status
object
2 properties 1 required
GetMetricRecordOutput
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dixa-analytics-api-openapi.yml Raw ↑

Other APIs Dixa publishes across the network.

Dixa Agents API
Dixa Anonymization API
Dixa Business Hours API
Dixa Chatbots API
Dixa Contact Endpoints API
Dixa Conversations API
Dixa Custom Attributes API
Dixa End Users API
Dixa Internal Notes API
Dixa Knowledge API
Dixa Messages API
Dixa Organization API
Where this information came from

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