Skip to main content
Swagger
All documentation pages

Security Considerations

  • Portal sends the email address of each organization member to your webhook URL. Portal never sends the email addresses of portal consumers outside your organization.
  • Portal signs every call so that your webhook can confirm the sender. Always verify the signature.
  • The token stays on the Portal server, tied to the member’s session. The token never reaches the browser, a cookie, or a page response. No one can use a stored token after the member logs out, and no other user on the same browser can use it.
  • Portal adds the token only to requests for allowed origins. Portal does not follow redirects on requests that carry the token. Portal returns a 3xx response from your API to the browser as a 502 error.
  • If a request already has its own Authorization header, Portal does not add the token.
  • Portal never forwards its own session cookie to your API.
  • Portal encrypts the signing secret at rest and shows it only once.

Was this page helpful?