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 Sessions & Bookings API

v1 scheduling-widget sessions and completed bookings

Avoca Sessions & Bookings API is one of 8 APIs that Avoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sessions & Bookings. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

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

7 operations 7 paths 4 schemas 7 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 Sessions & Bookings 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 7

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

Sessions & Bookings 7

v1 scheduling-widget sessions and completed bookings

GET
/api/v1/teams/{teamId}/schedulers
List schedulers
listSchedulers 1 param → 200403
GET
/api/v1/teams/{teamId}/sessions
List sessions
listTeamSessions 7 params → 200403
GET
/api/v1/teams/{teamId}/sessions/{sessionId}
Get a session
getTeamSession 2 params → 200404
GET
/api/v1/teams/{teamId}/bookings
List bookings
listTeamBookings 6 params → 200403
GET
/api/v1/teams/{teamId}/bookings/{bookingId}
Get a booking
getTeamBooking 2 params → 200404
GET
/api/v1/sessions
List sessions (cross-team)
listSessions 7 params → 200401
GET
/api/v1/bookings
List bookings (cross-team)
listBookings 6 params → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Session (16 properties), CursorPagination (3 properties), Error (2 properties), TeamMeta (1 property). Each schema is shown below with its type and property counts.

Error
object
2 properties 1 required
CursorPagination
object
3 properties
TeamMeta
object
1 property
Session
object
A customer's journey through the scheduling widget — from starting a booking to completing it or dropping off.
16 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avoca-sessions-bookings-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 Scheduler Analytics (v0) API
Avoca Teams API
Where this information came from

This is an independent, third-party profile of Avoca Sessions & Bookings 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.