Webhook Test Payloads

Generate realistic test webhook payloads for Stripe, GitHub, Slack, Twilio, SendGrid and Shopify, with the right headers and schema.

Pay by wallet (x402) AI-generated webhook-test-payload

Example

Input

{
  "service": "test_value",
  "event_type": "test_value"
}

Answer

{
  "headers": {
    "User-Agent": "Webhook-Delivery/1.0",
    "X-Timestamp": "1698765432",
    "Content-Type": "application/json",
    "X-Request-ID": "req_test_abc123xyz",
    "X-Webhook-Signature": "whsec_test_1234567890abcdef"
  },
  "payload": {
    "id": "evt_test_1234567890",
    "data": {
      "object": {
        "id": "test_obj_123",
        "value": "test_value_data",
        "object": "test_value",
        "status": "active",
        "created": 1698765432,
        "updated": 1698765432
      }
    },
    "type": "test_value",
    "object": "event",
    "created": 1698765432,
    "request": {
      "id": null,
      "idempotency_key": null
    },
    "livemode": false,
    "api_version": "2023-10-16",
    "pending_webhooks": 1
  },
  "service": "test_value",
  "event_type": "test_value",
  "documentation_url": "https://docs.example.com/webhooks/test_value"
}

Inputs

Field	Type	Required	What it is
`service`	string	Yes	stripe/github/slack/twilio/sendgrid/shopify
`event_type`	string	Yes	—

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`headers`	object	Always (present in every successful answer)
`payload`	object	Always (present in every successful answer)
`event_type`	string	Always (present in every successful answer)
`documentation_url`	string	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "webhook-test-payload",
    "inputs": {
      "service": "test_value",
      "event_type": "test_value"
    },
    "max_price_cents": 5
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "webhook-test-payload",
    "inputs": {
      "service": "test_value",
      "event_type": "test_value"
    },
    "max_price_cents": 5
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "webhook-test-payload",
  inputs: {
    "service": "test_value",
    "event_type": "test_value"
  },
  max_price_cents: 5,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="webhook-test-payload",
    inputs={
        "service": "test_value",
        "event_type": "test_value",
    },
    max_price_cents=5,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/webhook-test-payload?service=test_value&event_type=test_value'

Limitations

Provider-specific or versioned fields can differ
Generated payloads match common webhook schemas — provider-specific fields or versioned payload formats may differ
What to do instead: Compare generated payloads against the provider's webhook documentation and adjust field names as needed