Zoca Scheduling - Stripe Terminal API
The Scheduling - Stripe Terminal API from Zoca — 8 operation(s) for scheduling - stripe terminal.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/zoca:zoca-scheduling-stripe-terminal-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Zoca Platform Scheduling - Stripe Terminal API
description: 'The Zoca platform API behind the Zoca web app and mobile apps: scheduling, website generation, Google Business Profile, discovery/local SEO, social media, booking enquiries, offers, clients, staff, billing and the Zoca "brain" agent layer.'
version: 3.20.10
contact: {}
x-apievangelist-note: Harvested verbatim from https://api.zoca.ai/swagger.json. The provider ships the default NestJS Swagger metadata (title "API Documentation", empty servers[]); title/description/servers were set by API Evangelist for identification and the unmodified original is preserved at openapi/_original/zoca-platform-swagger.json. Every path, operation, summary, parameter and response is exactly as published.
servers:
- url: https://api.zoca.ai
description: Production
tags:
- name: Scheduling - Stripe Terminal
paths:
/scheduling/stripe/terminal/connection-token:
post:
operationId: t_value
parameters: []
responses:
'200':
description: ''
security:
- bearer: []
summary: Create Stripe Terminal connection token
tags:
- Scheduling - Stripe Terminal
/scheduling/stripe/terminal/tap-to-pay-config:
get:
operationId: getSchedulingStripeTerminalTapToPayConfig
parameters: []
responses:
'200':
description: ''
security:
- bearer: []
summary: Get Tap to Pay configuration
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/ensure-location:
post:
description: Creates a Stripe Terminal Location (tml_...) for the connected account using the stored address for locationEntityId, persists it to entities.locations, and returns it.
operationId: postSchedulingStripeTerminalEnsureLocation
parameters: []
responses:
'200':
description: ''
security:
- bearer: []
summary: Provision Stripe Terminal location for a connected account
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/readers/pair:
post:
operationId: postSchedulingStripeTerminalReadersPair
parameters: []
responses:
'201':
description: ''
security:
- bearer: []
summary: Pair a Stripe Terminal smart reader to a location
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/readers:
get:
operationId: getSchedulingStripeTerminalReaders
parameters: []
responses:
'200':
description: ''
security:
- bearer: []
summary: List paired Stripe Terminal readers for a location
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/readers/{id}:
patch:
operationId: patchSchedulingStripeTerminalReadersById
parameters: []
responses:
'200':
description: ''
security:
- bearer: []
summary: Rename a paired reader
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
delete:
operationId: deleteSchedulingStripeTerminalReadersById
parameters: []
responses:
'204':
description: ''
security:
- bearer: []
summary: Unpair a reader
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/readers/simulate:
post:
operationId: postSchedulingStripeTerminalReadersSimulate
parameters: []
responses:
'201':
description: ''
security:
- bearer: []
summary: (Test mode only) Create a simulated reader for QA
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
/scheduling/stripe/terminal/readers/{id}/present-payment-method:
post:
operationId: postSchedulingStripeTerminalReadersByIdPresentPaymentMethod
parameters: []
responses:
'204':
description: ''
security:
- bearer: []
summary: (Test mode only) Inject a test card scenario on a simulated reader
tags:
- Scheduling - Stripe Terminal
x-operation-id-source: normalized
x-operation-id-original: t_value
components:
securitySchemes:
access-token:
scheme: bearer
bearerFormat: JWT
type: http
name: Authorization
description: Enter JWT token in the format Bearer <token>
in: header