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

Zoca Scheduling - Policies API

The Scheduling - Policies API from Zoca — 18 operation(s) for scheduling - policies.

Zoca Scheduling - Policies API is one of 193 APIs that Zoca publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Scheduling - Policies. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 27 operations across 18 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 3.20.10.

Requests are made against a single base URL, https://api.zoca.ai.

27 operations 18 paths 1 schemas 4 DELETE14 GET5 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.20.10
Base URL
https://api.zoca.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zoca Scheduling - Policies API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token).

  • access-token — Enter JWT token in the format Bearer

Paths & Operations 27

Across 18 paths, the API surfaces 27 operations — 4 DELETE, 14 GET, 5 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Scheduling - Policies 27
POST
/scheduling/policies/fee
Create a new fee policy (cancellation or no-show)
t_value → 201
GET
/scheduling/policies/fee
List all fee policies
t_value 1 param → 200
GET
/scheduling/policies/fee/{id}
Get a fee policy by ID
t_value 1 param → 200404
PUT
/scheduling/policies/fee/{id}
Update a fee policy
t_value 1 param → 200404
DELETE
/scheduling/policies/fee/{id}
Delete a fee policy (soft delete)
t_value 1 param → 204404
GET
/scheduling/policies/fee/entity/{entityId}
Get fee policies for an entity
t_value 3 params → 200
GET
/scheduling/policies/fee/effective
Get effective fee policy with inheritance
t_value 5 params → 200
POST
/scheduling/policies/fee/deposit/preview
Preview service variations cheaper than a proposed fixed deposit
t_value → 200
GET
/scheduling/policies/effective-preference
Get the effective fee-policies preference for a specific client (F2 exemptions)
t_value 3 params → 200
GET
/scheduling/policies/fee/acknowledgment-text
Get policy acknowledgment texts
t_value 2 params → 200
POST
/scheduling/policies/payment
Create a new payment policy
t_value → 201
GET
/scheduling/policies/payment
List all payment policies
t_value → 200
GET
/scheduling/policies/payment/{id}
Get a payment policy by ID
t_value 1 param → 200404
PUT
/scheduling/policies/payment/{id}
Update a payment policy
t_value 1 param → 200404
DELETE
/scheduling/policies/payment/{id}
Delete a payment policy (soft delete)
t_value 1 param → 204404
GET
/scheduling/policies/payment/entity/{entityId}
Get payment policies for an entity
t_value 2 params → 200
POST
/scheduling/policies/booking
Create a new booking policy (advanced restrictions)
t_value → 201
GET
/scheduling/policies/booking
List all booking policies
t_value 1 param → 200
GET
/scheduling/policies/booking/{id}
Get a booking policy by ID
t_value 1 param → 200404
PUT
/scheduling/policies/booking/{id}
Update a booking policy
t_value 1 param → 200404
DELETE
/scheduling/policies/booking/{id}
Delete a booking policy (soft delete)
t_value 1 param → 204404
GET
/scheduling/policies/booking/entity/{entityId}
Get booking policies for an entity
t_value 2 params → 200
POST
/scheduling/policies/map
Map a policy to an entity
t_value → 201
DELETE
/scheduling/policies/map/{mappingId}
Remove a policy mapping
t_value 1 param → 204
PUT
/scheduling/policies/map/{mappingId}/default
Set a policy mapping as default
t_value 1 param → 200
GET
/scheduling/policies/map/policy/{policyId}
Get all mappings for a policy
t_value 2 params → 200
GET
/scheduling/policies/map/entity/{entityId}
Get all policy mappings for an entity
t_value 3 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is e (6 properties). Each schema is shown below with its type and property counts.

e
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoca-scheduling-policies-api-openapi.yml Raw ↑

Other APIs Zoca publishes across the network.

Zoca ACM API
Zoca Acuity API
Zoca Addon Groups API
Zoca Addons API
Zoca Aeo Lead Magnet API
Zoca Agents API
Zoca API Keys API
Zoca App API
Zoca App Blocker API
Zoca App Blocker Updates API
Zoca Approvals API
Zoca Auth API
Where this information came from

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