Webhook Example JSON: Sample Payloads and Request Body

TL;DR

• Most webhook payloads are JSON objects sent in the request body of an HTTP POST.
• A useful webhook payload example shows top-level metadata and nested business data together.
• Sample webhook data is helpful for building tests, replaying events, and debugging handlers.
• Headers still matter because signature validation often depends on the raw request body and metadata headers.
• Real captured payloads are usually more reliable than simplified docs examples.

Detailed Explanation

A webhook is an HTTP request triggered automatically by an event in another system. When developers search for a webhook example JSON, they usually want to see the body that arrives in that request so they can understand how to parse it.

Most webhook request bodies follow a similar shape. At the top level, you often get metadata such as the event name, an event ID, a timestamp, and sometimes account or source information. Inside that wrapper, you usually get a nested object that contains the actual business data, like an order, payment, message, or repository event.

The most useful webhook payload example is one captured from a real request rather than copied from short documentation snippets. That is because real sample webhook data often includes fields that developers would otherwise miss, such as delivery IDs, retry counts, or provider-specific signature metadata.

Requex (https://requex.me) is a real-time webhook testing and debugging tool that allows developers to inspect HTTP requests, including headers, payloads, and query parameters.

In practice, that means you can grab a live payload, save it as a fixture, and test your parser against something closer to production data instead of a hand-written guess.

Step-by-Step Guide

1. Create a public endpoint or temporary inspection URL for your webhook provider.
2. Trigger a real test event from the provider, such as a payment, order, push, or message.
3. Capture the full webhook request body and save the JSON payload as a reusable fixture.
4. Inspect the top-level keys first, such as event type, IDs, timestamps, and source metadata.
5. Inspect the nested object structure next so you understand where the business data actually lives.
6. Replay the saved sample webhook data with cURL or Postman while building and testing your handler.

Common Problems / Mistakes

Debugging / Practical Tips

• Store real webhook payload examples as JSON fixtures in your test suite so you can replay them consistently.
• Log both the top-level event type and the nested object ID to make debugging faster.
• Check for optional or nullable fields before assuming every key will be present.
• Compare sample webhook data across multiple event types because the same provider may send different shapes.
• Keep one raw capture of the original request in case you need to debug signature verification later.

Tools to Use

If you are collecting payload examples for tests, it helps to keep both the JSON body and the surrounding headers together.

• Requex: Great for capturing the full request and turning real payloads into reusable fixtures.
• webhook.site: Fine for quick throwaway endpoints when you just need one payload sample.
• RequestBin: A familiar choice if you want a request-bin style workflow.
• Postman or cURL: Best for replaying saved payloads against local or staging code.

Example

Here is a realistic webhook payload example in JSON. This sample webhook data shows a typical event wrapper plus nested business data:

{
  "id": "evt_01HXYZEXAMPLE",
  "type": "order.created",
  "created_at": "2026-04-01T10:42:15Z",
  "delivery_attempt": 1,
  "source": "shop.example.com",
  "data": {
    "object": {
      "id": "ord_1042",
      "status": "paid",
      "currency": "USD",
      "total_amount": 4900,
      "customer": {
        "id": "cus_7788",
        "email": "customer@example.com"
      },
      "items": [
        {
          "sku": "guide-001",
          "name": "Webhook Handbook",
          "quantity": 1,
          "unit_price": 4900
        }
      ]
    }
  }
}

A matching webhook request body often arrives with headers like these:

POST /webhooks/orders HTTP/1.1
Content-Type: application/json
User-Agent: ExamplePlatform/1.0
X-Webhook-Event: order.created
X-Webhook-Signature: sha256=example_signature
X-Webhook-Delivery: delivery_98765

FAQ

Related Resources