Webhook.site API

The Webhook.site API is public, free to use, doesn't require authentication and is relatively easy to use.

General Usage

Base URL: https://webhook.site.

You must set the Accept and Content-Type headers to application/json.

You must set the Api-Key header if you have a Webhook.site account.

Common Uses

• Create a Webhook.site URL
• Fetch or search data sent to a Webhook.site URL

Things to Note

• In this API documentation, URL parameters are prefixed with : (colon) to show which parameters must be changed by the user. You must not include this character in the URL.
• A Token ID refers to the ID of the Webhook.site URL/e-mail address, i.e., when your Webhook.site URL is https://webhook.site/00000000-0000-0000-0000-000000000000, the Token ID is then 00000000-0000-0000-0000-000000000000.
• In API URLs, you cannot use Token Aliases in place of the Token ID.
• Webhook.site API Keys must be specified using the Api-Key HTTP header.
• Fair use guidelines, rate limits, and other limitations apply as described by the Terms of Service.

Authentication

While many endpoints of the Webhook.site API are public and work without any authentication, some endpoints do require authentication, or will return a 401 Unauthorized status code.

API Key

An API Key can be generated in the Control Panel, and provides access to Tokens that are either a) password protected or b) require login.

API Keys have the same privileges as the user who created them.

API Keys must be specified in the Api-Key HTTP header.

Create API Key

Password

Warning

Password authentication is deprecated and will be removed in 2025. We recommend using API Keys.

If you have set a password on a Webhook.site URL/token, to access the API resources for that token, you can use either of the following methods:

1. Specify the password using the password query string: ?password=[your password]
2. Set the password using HTTP Basic Auth, using the Authorization header. More info

Common Usages

Get data sent to URL

To retrieve the data that's sent to a Webhook.site URL or Email, you'll want to use the Get Requests endpoint.

Create new URL/email address

To create a new token programmatically, you can use the API like this:

$ curl -X POST https://webhook.site/token

This will return information about the token in JSON format, including its UUID. Your URL will be available at the endpoint https://webhook.site/[token uuid].

If you are a Webhook.site Pro or Enterprise customer, you should provide an API key in order to associate the created token with your account automatically:

$ curl -X POST -H 'Api-Key: 00000000-0000-0000-0000-000000000000' https://webhook.site/token

More info here.

WebSocket

You can connect to Webhook.site's WebSocket server (wss://ws.webhook.site) and listen for incoming requests, emails and DNSHooks in your own application. If you listen to a token associated with a Webhook.site account, you must specify and API key. Alternatively, you can use Webhook.site CLI.

You can use the Laravel Echo library to connect, Node.js example below:

import Echo from "laravel-echo";
import client from "socket.io-client";

let apiKey = '000-000...';
let tokenId = '111-111...';

const headers = apiKey ? {'Api-Key': apiKey} : {};
const echo = new Echo.default({
    host: 'wss://ws.webhook.site',
    broadcaster: 'socket.io',
    client,
    auth: {headers}
})

let channel = echo.private(`token.${tokenId}`);

channel.listen('.request.created', (data) => {
    // console.log(data)
})

---

Last update: May 1, 2025 09:46:56