Getting started

Quickstart

Create a bin and read your first captured request in under a minute.

Pixelhooks gives you a throwaway URL that records every HTTP request sent to it — method, headers, body, query string, and path — so you can see exactly what a webhook or callback is sending before you build the receiving end. No account, no setup, no local server.

Every bin is anonymous. The bin id is an unguessable cuid and acts as the only key — anyone with the URL can see the requests, so treat it like a secret.

1. Create a bin

Make a POST to /api/bins. You get back a bin id and its creation time.

curl -X POST https://hooks.pixelhop.io/api/bins
# { "id": "abc123cuid", "createdAt": "2026-06-19T09:00:00.000Z" }

Your capture URL is the origin plus /h/ and the bin id:

https://hooks.pixelhop.io/h/abc123cuid

2. Send something to it

Point any webhook, script, or curl at the capture URL. Every HTTP method works, and so does any sub-path beneath the bin — /abc123cuid/webhooks/stripe is recorded against the same bin, with the path preserved.

curl -X POST https://hooks.pixelhop.io/h/abc123cuid/webhooks/stripe \
  -H 'content-type: application/json' \
  -d '{"event":"payment_intent.succeeded"}'
# OK

The capture endpoint always replies 200 OK — it never rejects a request, so the sender behaves exactly as it would against your real endpoint.

3. Read it back

List the bin's requests, newest first:

curl https://hooks.pixelhop.io/api/bins/abc123cuid/requests

[
  {
    "id": "req_1",
    "method": "POST",
    "path": "/webhooks/stripe",
    "query": "",
    "contentType": "application/json",
    "bodySize": 41,
    "truncated": false,
    "createdAt": "2026-06-19T09:00:05.000Z"
  }
]

Then fetch one request in full — headers, query, and the decoded body:

curl https://hooks.pixelhop.io/api/bins/abc123cuid/requests/req_1

That is the whole loop: create a bin, point a service at it, read what arrived.

What's next

The REST API reference documents every endpoint, the response shapes, and the retention and body-size limits.
Driving this from an AI agent? The MCP setup guide wires Pixelhooks into your agent so it can create bins and wait for requests without leaving the conversation.
Want your bins to stick around? Sign-in is optional — anonymous use stays the default — but if you create an account with an email and password (or GitHub/Google where configured), the bins you make are saved to a list you can come back to.