Webhook Call Behavior
Portal calls your webhook once for every successful login callback of an organization member. This includes silent logins and token refreshes, so your webhook can receive more than one call for each login.
- Portal calls the webhook asynchronously, so login doesn’t wait for the response. Until the response arrives, Try It Out requests go out without a token.
- If the webhook doesn’t respond within three seconds, returns an error, or returns an invalid response, Portal stores no token for that session. Portal doesn’t display an error to the member. Portal records the failure only in its server logs.
- Portal stores the token for the duration of the session and does not refresh it. Portal requests a new token only at the next login callback.
- Your system controls the token lifetime. If a token expires before the session ends, requests to your API return 401 until the member logs in again. Set the token lifetime to match the session length that you expect.