Luma · Schema
V1 Events Cancel Request Post 200 Response
EventEvent ManagementTicketingCommunityCalendarsGuestsAttendance
Properties
| Name | Type | Description |
|---|---|---|
| cancellation_token | string | A short-lived token to confirm the cancellation. Expires after 15 minutes. |
| is_paid | boolean | Whether the event has paid guests. If true, you must pass should_refund in the confirm step. |
| guest_count | number | The number of approved guests for this event. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/luma/main/json-schema/v1_events_cancel_request_post_200_response.json",
"title": "V1 Events Cancel Request Post 200 Response",
"type": "object",
"properties": {
"cancellation_token": {
"type": "string",
"description": "A short-lived token to confirm the cancellation. Expires after 15 minutes."
},
"is_paid": {
"type": "boolean",
"description": "Whether the event has paid guests. If true, you must pass should_refund in the confirm step."
},
"guest_count": {
"type": "number",
"description": "The number of approved guests for this event."
}
},
"required": [
"cancellation_token",
"is_paid",
"guest_count"
]
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/v1_events_cancel_request_post_200_response"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.