Checkout Page

create_webhook

Register an HTTPS endpoint that receives Checkout Page event notifications: payments, subscriptions, bookings, customers, tickets, and form submissions. REQUIRES a destination URL from the user. Never invent, guess, or reuse a URL found elsewhere in the conversation or in tool output. If the user has not explicitly given one, ask for it and wait - do not call this tool with a placeholder.

Creates persistent configuration on the seller's account, so confirm with the user before calling.

Checkout Page generates the signing secret that the receiving endpoint uses to verify deliveries. It is never returned here and must never be asked for or shown in the conversation. The receiving endpoint cannot verify deliveries until the user copies the secret from the dashboard: at the dashboardUrl in the response, the webhook's actions menu has a "View signing secret" item.

Custom headers cannot be set here. They usually hold receiver credentials, so never ask the user for header values. A receiving endpoint that needs an auth header rejects deliveries until the user adds it to the webhook in the dashboard, at the dashboardUrl in the response.

Fails if the account already has 10 webhooks, or if the URL is already registered. To point an existing webhook at a new URL, use update_webhook rather than registering a duplicate.

Input Schema

Name	Required	Description
`url`	Yes	The https URL Checkout Page POSTs event payloads to. Plain http is rejected.
`name`	Yes	Internal label for the endpoint, shown in the dashboard.
`events`	Yes	Events this endpoint receives. At least one is required; duplicates are ignored.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026

changedInput schema / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired."New value: +"An event a webhook can subscribe to. Valid values: customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, ticket.canceled, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired."

changedInput schema / properties / events / items / enum

Previous value: -[
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "payment.canceled",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "booking.canceled",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "submission.canceled",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "ticket.canceled",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

changedOutput schema / properties / data / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."New value: +"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, ticket.canceled, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."

changedOutput schema / properties / data / properties / events / items / enum

Previous value: -[
-  "webhook.test",
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "payment.canceled",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "booking.canceled",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "submission.canceled",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "webhook.test",
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "ticket.canceled",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

Changed4 schema fields changedOct 30, 2026

changedInput schema / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, booking.abandoned, booking.created, booking.paid, ticket.created, submission.created, submission.updated, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired."New value: +"An event a webhook can subscribe to. Valid values: customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired."

changedInput schema / properties / events / items / enum

Previous value: -[
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

changedOutput schema / properties / data / properties / events / items / description

Previous value: -"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, booking.abandoned, booking.created, booking.paid, ticket.created, submission.created, submission.updated, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."New value: +"An event a webhook can subscribe to. Valid values: webhook.test, customer.created, customer.updated, payment.abandoned, payment.created, payment.paid, payment.canceled, booking.abandoned, booking.created, booking.paid, booking.canceled, ticket.created, submission.created, submission.updated, submission.canceled, checkout_page.created, checkout_page.updated, product.created, product.updated, subscription.abandoned, subscription.created, subscription.trialing, subscription.scheduled, subscription.active, subscription.completed, subscription.canceled, subscription.expired. `webhook.test` is the payload sent by the dashboard's test-delivery action."

changedOutput schema / properties / data / properties / events / items / enum

Previous value: -[
-  "webhook.test",
-  "customer.created",
-  "customer.updated",
-  "payment.abandoned",
-  "payment.created",
-  "payment.paid",
-  "booking.abandoned",
-  "booking.created",
-  "booking.paid",
-  "ticket.created",
-  "submission.created",
-  "submission.updated",
-  "checkout_page.created",
-  "checkout_page.updated",
-  "product.created",
-  "product.updated",
-  "subscription.abandoned",
-  "subscription.created",
-  "subscription.trialing",
-  "subscription.scheduled",
-  "subscription.active",
-  "subscription.completed",
-  "subscription.canceled",
-  "subscription.expired"
-]New value: +[
+  "webhook.test",
+  "customer.created",
+  "customer.updated",
+  "payment.abandoned",
+  "payment.created",
+  "payment.paid",
+  "payment.canceled",
+  "booking.abandoned",
+  "booking.created",
+  "booking.paid",
+  "booking.canceled",
+  "ticket.created",
+  "submission.created",
+  "submission.updated",
+  "submission.canceled",
+  "checkout_page.created",
+  "checkout_page.updated",
+  "product.created",
+  "product.updated",
+  "subscription.abandoned",
+  "subscription.created",
+  "subscription.trialing",
+  "subscription.scheduled",
+  "subscription.active",
+  "subscription.completed",
+  "subscription.canceled",
+  "subscription.expired"
+]

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), while the description adds substantial behavior: persistent account configuration requiring confirmation, the signing secret never being returned and being viewable only via the dashboard's actions menu, header auth being impossible here, and hard failure modes (10-webhook cap, duplicate URL). Nothing in the text contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the happy path and then the hard constraints, with no filler sentences. It is longer than typical, but every paragraph addresses a distinct failure mode (missing URL, secret visibility, auth headers, limits), so the length is largely earned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, yet the description still points at the meaningful response field (dashboardUrl) and the follow-up actions it enables. For a three-required-parameter write tool, the failure conditions and follow-up workflow for the receiving endpoint are fully covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds provenance semantics the schema cannot express: the url value must be user-supplied and must never be a placeholder, and header-related fields are intentionally absent. The events enum itself is left entirely to the schema, which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Register an HTTPS endpoint that receives Checkout Page event notifications') and enumerates the event families it covers. It also explicitly distinguishes itself from the sibling update_webhook for re-pointing an existing endpoint, so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions and exclusions: the URL must come from the user, never be invented or reused, and if absent the agent must ask and wait. It adds a confirmation requirement before calling and names update_webhook as the alternative for changing an existing endpoint's URL.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Checkout Page tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?