Skip to content

Webhook.site API

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

Note

Please note that fair use guidelines and other limitations apply as described by the Terms of Service.

General Usage

Base URL: https://webhook.site.

We recommend that you set the Accept and Content-Type headers to application/json.

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.

For example, with cURL, this returns the 50 latest requests in JSON format.

curl https://webhook.site/token/a2a6a4ae-4130-4063-953a-84fa29d81d43/requests

More info here.

Create new URL/email address

In the Webhook.site API, this is referred to as a token. To create a new one 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.

Authentication

While most functions in the Webhook.site API work without any authentication whatsoever, 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.

To specify an API Key in a request, use the Api-Key HTTP header: Api-Key: [your API Key]

Password

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