Pathfix Webhooks

generated: '2026-10-18'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.pathfix.com/webhooks-preview.md
sources:
- https://docs.pathfix.com/webhooks-preview.md
- https://pathfix.com/blog/adding-user-facing-webhook-integration-in-your-saas-platform/
- https://docs.pathfix.com/event-callback.md
- https://docs.pathfix.com/events.md
description: Pathfix provides webhook‑like event callbacks and client‑side events.
events:
- event: USER_CONSENT_SUCCESS
  description: When a user connection is successful made i.e. a user has successfully connected his provider account to your application.
- event: USER_CONSENT_FAILURE
  description: When a user connection has failed i.e. the oauth connection to the users account has failed.
- event: USER_CONSENT_DISCONNECT
  description: When a user has disconnected their account.
- event: CALL_FORMAT_ERROR
  description: There is an error in the API call format e.g. malformed JSON.
- event: API_ERROR
  description: The provider has returned an error in the API. Check the API structure as specified by the provider and try again.
- event: INVALID_OAUTHID
  description: When an API call is attempted before a user has authenticated your app i.e. user does not have a valid oauth connection.
- event: consented
  description: The event fires immediately after your user successfully authorizes with an Integration provider.
- event: consentRedirect
  description: The event fires when the user is redirected for consent during the OAuth flow.
- event: notConsented
  description: The event fires if the user starts the OAuth authorization process but does not complete the authorization successfully or closes
    the window midway.
- event: revoked
  description: The event fires when a previously granted consent is revoked.
- event: integrations
  description: The event fires after configurations are loaded and the $pinc.oauth component is ready to work with.
delivery: {}
docs: https://docs.pathfix.com/webhooks-preview.md