Webhook Security

Add an extra layer of security to your webhook events.

To prevent unauthorised users from posting content to your webhook, customers can enable adding an Authorization header to the requests sent through the Railz Dashboard.

To enable additional security for your webhooks:

  1. Open the Railz Dashboard™ and log in.
  2. In the left sidebar navigation menu, go to Developers > Webhooks.
  3. Expand the Authorization Header menu.
  4. Select the Bearer and enter the required information. By default, No Authorization is selected.
Enable Authorization header for webhooks. Click to Expand.Enable Authorization header for webhooks. Click to Expand.

Enable Authorization header for webhooks. Click to Expand.

Bearer Authorization

Railz supports Bearer tokens as an Authorization header in webhook responses.

🚧

You will need to provide us with a public API endpoint that accepts Basic authentication using a username and password.

Railz Bearer Authorization header. Click to Expand.Railz Bearer Authorization header. Click to Expand.

Railz Bearer Authorization header. Click to Expand.

FieldValid values
Access Token URLA valid GET or POST API endpoint URL.
UsernameBasic Auth username.
PasswordBasic Auth password.
Token Response FieldThe name of the parameter in the provided API endpoint response that contains the access token.
Body Parameters (optional)Add up to 5 unique body parameters to include in your authentication endpoint request.
Header Parameters (optional)Add up to 5 unique header parameters to include in your authentication endpoint request.

Reserved Header Parameter Names

Railz-Signature, Railz-API-Version, and authorization are reserved header parameter names and can't be added.