Webhooks & API overview

Pocketsflow exposes events from your business so you can connect them to your own tools and workflows. Today, this is primarily done through webhooks, with a more complete HTTP API planned for the future.

​

What you can do with webhooks

Webhooks let Pocketsflow notify your systems when important events happen, such as:

• A new order is created.
• A payout is initiated.
• A subscription renews or is canceled.
• A refund is issued.

You can use these events to:

• Update internal dashboards and CRMs.
• Grant or revoke access in external systems.
• Trigger emails or messages in your own infrastructure.

​

High-level architecture

At a high level:

1. You register a webhook endpoint URL in your Pocketsflow settings.
2. When an event occurs, Pocketsflow sends an HTTP POST request to that URL.
3. Your server receives the payload, verifies authenticity, and processes it.
4. You return a 2xx status code to acknowledge receipt.

If your server is temporarily unavailable, Pocketsflow can retry delivery according to its retry policy.

​

Webhooks and the HTTP API

Pocketsflow gives you two complementary programmatic surfaces:

• Webhooks push events to you the moment they happen (a sale completes, a subscription renews, a refund is issued).
• The HTTP API lets you read and write data on demand — list orders, create products, create checkout sessions, register webhooks, and more.

Both are available today. A typical integration uses them together: react to a webhook, then call the API to fetch extra detail or take a follow-up action.

​

Where to go next

• API reference – base URL, API keys, and the full interactive reference.
• Authentication & security – verifying webhook signatures and securing your endpoint.
• Webhook events – which events are available and what their payloads look like.
• Consuming webhooks – best practices for handling delivery, retries, and idempotency.
• Integrations – connect Pocketsflow to platforms like WooCommerce.