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 - Stripe Terminal API

The Scheduling - Stripe Terminal API from Zoca — 8 operation(s) for scheduling - stripe terminal.

Zoca Scheduling - Stripe Terminal 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 - Stripe Terminal. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 8 paths. 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.

9 operations 8 paths 0 schemas 1 DELETE2 GET1 PATCH5 POST

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 - Stripe Terminal 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 9

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

Scheduling - Stripe Terminal 9
POST
/scheduling/stripe/terminal/connection-token
Create Stripe Terminal connection token
t_value → 200
GET
/scheduling/stripe/terminal/tap-to-pay-config
Get Tap to Pay configuration
t_value → 200
POST
/scheduling/stripe/terminal/ensure-location
Provision Stripe Terminal location for a connected account
t_value → 200
POST
/scheduling/stripe/terminal/readers/pair
Pair a Stripe Terminal smart reader to a location
t_value → 201
GET
/scheduling/stripe/terminal/readers
List paired Stripe Terminal readers for a location
t_value → 200
PATCH
/scheduling/stripe/terminal/readers/{id}
Rename a paired reader
t_value → 200
DELETE
/scheduling/stripe/terminal/readers/{id}
Unpair a reader
t_value → 204
POST
/scheduling/stripe/terminal/readers/simulate
(Test mode only) Create a simulated reader for QA
t_value → 201
POST
/scheduling/stripe/terminal/readers/{id}/present-payment-method
(Test mode only) Inject a test card scenario on a simulated reader
t_value → 204

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoca-scheduling-stripe-terminal-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 - Stripe Terminal 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.