Skip to main content
Swagger
All documentation pages

Overview

  • You enter a webhook URL, generate a signing secret, turn on the feature, and apply your changes.
  • After a member logs in, Portal sends a signed POST request that contains the member’s email address to your webhook. Login never waits for the webhook.
  • Portal stores the response from your webhook on the server for that member’s session.
  • When the member sends a request from Try It Out, the Portal proxy adds Authorization: Bearer <token> to the request. The proxy adds the header only if the request goes to an allowed origin and doesn’t already have a non-empty Authorization header.

Was this page helpful?