Developer guide
Heads up: we keep a copy of everything. Each request you send here, and each response we send back, is saved in full: headers, bodies and parameters. We also save your IP address, about where you are, your internet provider, what software sent the request, and a fingerprint of the secure connection. We never delete it. Webhook payloads often carry API keys, signing secrets and customer details, so please use test data. By using webhook.plus you agree to this. Read the data notice
A friendly webhook and HTTP testing tool. Get a personal endpoint, send test requests, and see exactly what arrived. Free, with no account.
All of these live at https://webhook.plus. You don't need an account or a key, and we don't rate-limit you. Browser code on any site can call them. If you'd like the full spec, it's in our OpenAPI file. Using an AI tool? Point it at our guide for AI tools.
You can send JSON, a regular form, or a raw body. If something goes wrong, you'll get JSON back with success: false, plus error.status and error.message, so your code can tell what happened.
GET /base64
Turn base64 back into text, or text into base64 with mode=encode. Standard and URL-safe base64 both work.
data query- The text to decode or encode.
mode query- decode (the default) or encode. Default:
"decode". Allowed: decode, encode. content_type query- The Content-Type we use for the reply. Default:
"text/plain; charset=utf-8".
POST /base64
Same as the GET version, but you send the input in the body. A plain text/plain body works too.
data body- The text to decode or encode.
mode body- decode (the default) or encode. Default:
"decode". Allowed: decode, encode. content_type body- The Content-Type we use for the reply. Default:
"text/plain; charset=utf-8".
GET /base64/{encoded}
Put base64 right in the URL path and we decode it for you. URL-safe base64 is the comfiest choice here.
encoded path · required- The base64 you want decoded.
content_type query- The Content-Type we use for the reply.
GET /reply
Pick the status, body, content type and headers we reply with, plus an optional delay of up to 10 seconds. HTML bodies can run JavaScript, in an isolated origin.
status query- The status we reply with (200 to 599). Default:
200. body query- What you want the reply body to say.
base64 query- A binary body for the reply, written as base64. If you send both, this wins over body.
content_type query- The Content-Type we use for the reply. Default:
"text/plain; charset=utf-8". headers query- Response headers as name/value pairs. With GET, send them as a JSON-encoded object.
delay query- Seconds to wait before we start replying (up to 10). Default:
0.
POST /reply
Same as GET /reply, with your choices sent in the body instead. HTML bodies can run JavaScript, in an isolated origin.
status body- The status we reply with (200 to 599). Default:
200. body body- What you want the reply body to say.
base64 body- A binary body for the reply, written as base64. If you send both, this wins over body.
content_type body- The Content-Type we use for the reply. Default:
"text/plain; charset=utf-8". headers body- Response headers as name/value pairs. With GET, send them as a JSON-encoded object.
delay body- Seconds to wait before we start replying (up to 10). Default:
0.
GET /recipe/{directives}
Build a reply right in the path, e.g. /recipe/s=201/h=content-type:text%2Fplain/b64=SGVsbG8=. Ingredients: s (status), h (header), c (cookie), r (redirect), b64 (body) and end. Go templates are not supported.
directives path · required- Your recipe: directives separated by slashes. URL-encode any value that contains a slash.
GET /get
Send a GET and we show you what arrived: method, query, headers, body, parsed JSON, form fields and multipart files.
POST /post
Send a POST and we show you what arrived: method, query, headers, body, parsed JSON, form fields and multipart files.
PUT /put
Send a PUT and we show you what arrived: method, query, headers, body, parsed JSON, form fields and multipart files.
PATCH /patch
Send a PATCH and we show you what arrived: method, query, headers, body, parsed JSON, form fields and multipart files.
DELETE /delete
Send a DELETE and we show you what arrived: method, query, headers, body, parsed JSON, form fields and multipart files.
GET /anything
Your all-purpose webhook endpoint. Any method and any path below /anything/ works, and we echo back the method, query, headers, body, parsed JSON, form fields and files.
POST /anything
POST to /anything (or any path below it) and we echo back the method, query, headers, body, parsed JSON, form fields and files.
GET /any
A shorter twin of /anything: any method works, and we echo back the method, query, headers, body, parsed JSON, form fields and files.
POST /any
POST to /any and we echo back the method, query, headers, body, parsed JSON, form fields and files.
GET /payload
Sends your request body straight back, byte for byte, with the same Content-Type you used.
POST /payload
POST a body and get it straight back, byte for byte, with the same Content-Type you used.
GET /headers
See just the headers your request arrived with, as JSON.
GET /ip
See the IP address your request came from, as JSON.
GET /user-agent
See the User-Agent your client sent, as JSON.
GET /uuid
Get a fresh random UUID.
GET /cookies
See the cookies your request carried, as JSON.
GET /bearer
Check that your client sends an Authorization: Bearer header. Any token passes; no token gets a 401.
GET /json
A small sample JSON response.
GET /html
A small sample HTML page.
GET /xml
A small sample XML document.
GET /gzip
Echoes your request back as gzip-compressed JSON, to check that your client decompresses it.
GET /deflate
Echoes your request back as deflate-compressed JSON, to check that your client decompresses it.
GET /status/{codes}
Reply with the status you ask for (200 to 599). Give a comma-separated list and we pick one at random.
codes path · required- The status to reply with, or a comma-separated list for us to pick from at random.
GET /delay/{seconds}
Wait the number of seconds you choose (up to 10), then echo your request.
seconds path · required- How many seconds to wait (up to 10; fractions are fine).
GET /bytes/{count}
Get up to 1 MiB of random bytes.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
GET /stream/{count}
Stream 1 to 100 newline-delimited JSON records.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
GET /redirect/{count}
Redirect the number of times you choose (up to 20), ending at /get, which echoes your request.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
GET /relative-redirect/{count}
Like /redirect/{count}, but each Location header is a relative path.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
GET /absolute-redirect/{count}
Like /redirect/{count}, but each Location header is a full URL.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
GET /cache/{age}
Echo your request with a Cache-Control max-age you choose, and answer conditional requests (If-None-Match, If-Match) with 304 or 412.
age path · required- How long, in seconds, the reply may be cached (sent as Cache-Control max-age).
GET /etag/{etag}
Reply with the ETag you choose, so you can test If-None-Match (304) and If-Match (412).
etag path · required- The entity tag to use, without quotes.
GET /response-headers
Every query parameter you send comes back as a response header. Headers the runtime manages itself are left out.
GET /redirect-to
Redirect to any HTTP(S) URL or relative path, with the redirect status of your choice.
url query · required- Where to send the redirect: a public HTTP(S) URL or a relative path.
status_code query- The redirect status: 301, 302, 303, 307 or 308. Default:
302.
GET /basic-auth/{username}/{password}
Check that your client sends HTTP Basic auth with the username and password in the path. Wrong or missing credentials get a 401.
username path · required- The username your client should send.
password path · required- The password your client should send.
GET /bearer/{expectedToken}
Check that your client sends Authorization: Bearer with exactly the token in the path. Anything else gets a 401.
expectedToken path · required- The token your client should send in Authorization: Bearer.
GET /cookies/set
Sets a cookie for each query parameter (name=value), then redirects you to /cookies.
GET /cookies/delete
Clears the cookies named in the query string, then redirects you to /cookies.
GET /drip
Sends bytes slowly, one at a time, spread over the duration you choose. Duration plus delay can be up to 10 seconds in total.
duration query- Seconds to spread the stream over (up to 10, together with delay).
delay query- Seconds to wait before we start replying (up to 10).
numbytes query- How many bytes to drip. Default:
10. count query- How many you want: bytes, records, events, redirects or links, depending on the endpoint. Default:
5. code query- The status we stream back with (200 to 599). Default:
200.
GET /drip-lines
Like /drip, but each byte arrives on its own line. Duration plus delay can be up to 10 seconds in total.
duration query- Seconds to spread the stream over (up to 10, together with delay).
delay query- Seconds to wait before we start replying (up to 10).
numbytes query- How many bytes to drip. Default:
10. count query- How many you want: bytes, records, events, redirects or links, depending on the endpoint. Default:
5. code query- The status we stream back with (200 to 599). Default:
200.
GET /sse
Streams server-sent events, spread over the duration you choose. Duration plus delay can be up to 10 seconds in total.
duration query- Seconds to spread the stream over (up to 10, together with delay).
delay query- Seconds to wait before we start replying (up to 10).
numbytes query- How many bytes to drip. Default:
10. count query- How many you want: bytes, records, events, redirects or links, depending on the endpoint. Default:
5. code query- The status we stream back with (200 to 599). Default:
200.
GET /links/{count}/{offset}
A small HTML page of numbered links to its sibling pages, handy for testing crawlers.
count path · required- How many you want: bytes, records, events, redirects or links, depending on the endpoint.
offset path · required- Which link is the current page (shown as plain text, not a link).
GET /docs
Our developer guide, as a friendly HTML page.
GET /robots.txt
What crawlers may visit, and where to find our sitemap.
GET /sitemap.xml
A list of our public pages for search engines.
GET /health
A quick "we're up" check. It doesn't test anything beyond this service.
GET /llms.txt
A plain-text guide to webhook.plus for AI tools.