wakato-io Bookings API
The Bookings API from wakato-io — 3 operation(s) for bookings.
The Bookings API from wakato-io — 3 operation(s) for bookings.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/wakato-io:wakato-io-bookings-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Wakato Space Bookings API
version: 1.0.0
description: 'The **Wakato Space API** lets an external agent or tool (Claude Code, Cursor,
Zapier, a partner integration, your own scripts) operate a single Wakato
**Space** using a scoped Bearer token (a *Space API key*, `wks_live_…`).
The **same token** works two ways:
- **REST** — the endpoints documented here (`/functions/v1/space-api/…`).
- **MCP** — a Model Context Protocol server at `/functions/v1/space-mcp`
that exposes the same operations as tools to MCP clients. MCP clients
self-discover the tools via `tools/list`; see the Quickstart to connect.
### Authentication
Send the key as a Bearer token: `Authorization: Bearer wks_live_…`.
A key is locked to exactly one Space and cannot read or write any other
Space, the wallet (beyond read), member permissions, or other users.
### Scopes
Every key grants per-domain scopes with up to three actions:
- `read` — list / inspect
- `write` — create / edit
- `run` — the *consequential* action (publish a page, send an SMS, post
socially, run an automation). Public/billable actions are deliberately
split into `run` so you grant them explicitly.
Each operation below notes its required scope via `x-required-scope`.
A call without the scope returns `403`.
### Safety model
- Wallet, Finance, Integrations are **read-only**. Money is never moved.
- Secrets returns **names only** — values are never exposed.
- Social posts and ad campaigns default to **drafts**; going live requires
the `run` scope. Connecting new OAuth accounts is never done by a key.'
servers:
- url: https://api.wakato.io/functions/v1/space-api
description: Production
- url: https://pnwxrleocjbcvrrwrycq.supabase.co/functions/v1/space-api
description: Development
security:
- bearerAuth: []
tags:
- name: Bookings
paths:
/bookings:
get:
tags:
- Bookings
summary: List booked appointments (guest, start/end, status) across the space or one page
x-required-scope: pages:read
parameters:
- in: query
name: booking_page_id
schema:
type: string
- in: query
name: status
schema:
type: string
enum:
- confirmed
- cancelled
- in: query
name: upcoming_only
schema:
type: boolean
- in: query
name: from
schema:
type: string
description: ISO datetime
- in: query
name: to
schema:
type: string
description: ISO datetime
- in: query
name: search
schema:
type: string
description: Guest name or email
- in: query
name: limit
schema:
type: integer
responses:
'200':
$ref: '#/components/responses/Ok'
description: '**Required scope:** `pages:read`'
x-codeSamples:
- lang: bash
label: cURL
source: "curl -X GET \"https://api.wakato.io/functions/v1/space-api/bookings\" \\\n -H \"Authorization: Bearer wks_live_YOUR_TOKEN\""
operationId: getBookings
x-operation-id-source: derived
/bookings/{id}/cancel:
parameters:
- in: path
name: id
required: true
schema:
type: string
post:
tags:
- Bookings
summary: Cancel a booked appointment (guest is NOT auto-notified)
x-required-scope: pages:write
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
delete_calendar_event:
type: boolean
description: Also remove the linked calendar event (default false)
responses:
'200':
$ref: '#/components/responses/Ok'
description: '**Required scope:** `pages:write`'
x-codeSamples:
- lang: bash
label: cURL
source: "curl -X POST \"https://api.wakato.io/functions/v1/space-api/bookings/b7e4a1c2-9d3f-4e8a-b2c1-5f6d7e8a9b0c/cancel\" \\\n -H \"Authorization: Bearer wks_live_YOUR_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{}'"
operationId: postBookingsByIdCancel
x-operation-id-source: derived
/bookings/{id}/reschedule:
parameters:
- in: path
name: id
required: true
schema:
type: string
post:
tags:
- Bookings
summary: Move a confirmed booking to a new slot (validated against real availability…
x-required-scope: pages:write
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- new_date
- new_start
properties:
new_date:
type: string
description: YYYY-MM-DD in the page's timezone
new_start:
type: string
description: HH:MM in the page's timezone
new_end:
type: string
description: HH:MM — derived from duration when omitted
skip_availability_check:
type: boolean
responses:
'200':
$ref: '#/components/responses/Ok'
description: '**Required scope:** `pages:write`'
x-codeSamples:
- lang: bash
label: cURL
source: "curl -X POST \"https://api.wakato.io/functions/v1/space-api/bookings/b7e4a1c2-9d3f-4e8a-b2c1-5f6d7e8a9b0c/reschedule\" \\\n -H \"Authorization: Bearer wks_live_YOUR_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"new_date\": \"2026-06-15T10:00:00Z\",\n \"new_start\": \"example\"\n}'"
operationId: postBookingsByIdReschedule
x-operation-id-source: derived
components:
responses:
Ok:
description: Success
content:
application/json:
schema:
type: object
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: A Space API key, e.g. `wks_live_…`.