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

Avoca Scheduler Analytics (v0) API

Simple Scheduler analytics — legacy flat endpoints

Avoca Scheduler Analytics (v0) API is one of 8 APIs that Avoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Scheduler Analytics (v0). The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

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

Requests are made against a single base URL, https://enterprise-api.avoca.ai.

4 operations 4 paths 6 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.0
Base URL
https://enterprise-api.avoca.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Avoca Scheduler Analytics (v0) API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API key in the format avoca

Paths & Operations 4

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

Scheduler Analytics (v0) 4

Simple Scheduler analytics — legacy flat endpoints

GET
/api/scheduler-analytics
Get scheduler analytics
getSchedulerAnalytics 8 params → 200400401
GET
/api/scheduler-analytics/summary
Get scheduler analytics summary
getSchedulerAnalyticsSummary 2 params → 200401
GET
/api/simple_scheduler_booking_requests
List Simple Scheduler booking requests
listSimpleSchedulerBookingRequests 7 params → 200400401
GET
/api/simple_scheduler_config
List Simple Scheduler configs
listSimpleSchedulerConfigs 2 params → 200403

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SchedulerAnalytics (8 properties), UtmRow (7 properties), SchedulerConfig (5 properties), PeriodSummary (3 properties). Each schema is shown below with its type and property counts.

SchedulerConfig
object
5 properties
UtmRow
object
7 properties
Error
object
2 properties 1 required
OffsetPagination
object
3 properties
PeriodSummary
object
3 properties
SchedulerAnalytics
object
Metric blocks are present only when requested via the metrics parameter (default: all).
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avoca-scheduler-analytics-v0-api-openapi.yml Raw ↑

Other APIs Avoca publishes across the network.

Avoca Analytics (v1) API
Avoca Calls API
Avoca Coach API
Avoca Leads API
Avoca Outbound Texting API
Avoca Sessions & Bookings API
Avoca Teams API
Where this information came from

This is an independent, third-party profile of Avoca Scheduler Analytics (v0) 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.