Webhook authentication: bearer token and OAuth 2.0

Every webhook request carries the Parasend-Signature header, which proves it came from Parasend. If your endpoint sits behind a gateway that also requires its own credentials, Parasend can send them too.

The options

Authentication at your end What Parasend sends
None Only the signature (Parasend-Signature), which is always there.
Static bearer token An Authorization: Bearer … header with a token you give Parasend.
OAuth 2.0 Parasend gets an access token from your authorisation server with the client credentials you give it, and sends it as a bearer token. It fetches a new token when the old one expires.
A webhook set up with OAuth 2.0

Set it up

  1. Create or edit the webhook (see Set up a webhook).
  2. Under Authentication at your end, choose Static bearer token or OAuth 2.0.
  3. Fill in the token, or the OAuth 2.0 token URL, client ID, client secret and (if needed) scope.
  4. Save the webhook.

Always verify the signature as well: the bearer token proves the request was allowed through your gateway, the signature proves it came from Parasend and wasn't changed.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.