Skip to main content
Welcome to the storekit developer documentation. This section covers everything you need to build integrations with storekit.
Webhooks are the primary way to integrate with storekit. Direct API access is currently in early access and not widely available.

Requesting API Access

The API is not publicly available yet, and access is granted case by case while it is in early access. To request it, fill in the storekit MCP/API Access Request form. Include:
  • What you’re building and the problem it solves
  • Which stores or account the integration is for
  • The data or actions you need (for example reading orders, updating item availability)
  • Expected volume of requests
The storekit team reviews each request and issues API keys during onboarding. If you have a non-technical question about access, contact support.
Most integrations do not need the API. If you only need to react to what happens in your stores, webhooks need no approval process — they are a subscription feature you enable yourself under SettingsDevelopers.

Webhooks

Webhooks allow you to receive real-time notifications when events occur in your storekit stores. Use webhooks to:
  • Sync orders to your POS, kitchen display, or inventory system
  • Trigger automations when orders are placed, accepted, or completed
  • Monitor store status and printer connectivity
  • Track payouts to your bank accounts
  • Receive payment link payments when a customer pays via a shared payment link

Webhooks Overview

Learn how webhooks work and how to set them up.

Webhook Events

Browse all available event types and payloads.

Verifying Signatures

Secure your integration by verifying webhook authenticity.

Troubleshooting

Fix common webhook issues.

Ordering Agents

Ordering pages expose their capabilities to a customer’s AI agent directly: WebMCP tools for an agent in the customer’s browser, a remote MCP endpoint for an assistant elsewhere, a UCP profile for a commerce platform, and llms.txt for crawlers. All four face the customer and none of them need API access. The two MCP surfaces read a menu and fill a basket; the UCP profile and llms.txt are read-only. Store operations stay with the dashboard, the webhooks above and the REST API.

Ordering Agents Overview

The four customer-side surfaces and which one your reader wants.

WebMCP Tools

The tools an ordering page registers with the browser.

Getting Started

  1. Set up an endpoint - Create an HTTPS endpoint in your application to receive webhooks
  2. Register your endpoint - Add your endpoint URL in the storekit dashboard
  3. Verify signatures - Implement signature verification for security
  4. Handle events - Process incoming webhooks and respond with a 2xx status
storekit uses Svix for reliable webhook delivery. You can use the Svix libraries to simplify signature verification.