Connection CreatedWebhook
Event broadcast when a connection has been created.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection UpdatedWebhook
Event broadcast when a connection has been updated.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection DisabledWebhook
Event broadcast when a connection has been disabled.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection DeletedWebhook
Event broadcast when a connection has been deleted.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection CallableWebhook
Event broadcast when a connection is now callable.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection RevokedWebhook
Event broadcast when a connection has been revoked.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection Token Refresh FailedWebhook
Event broadcast when a connection token refresh has failed.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection Token Refresh PendingWebhook
Event broadcast when a connection has been token refresh pending.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event
Connection Token Refresh RecoveredWebhook
Event broadcast when a connection has been token refresh recovered.
Header parameters
The type of event that was triggered
HMAC SHA-256 signature of the request body, used to verify the webhook came from Apideck
A unique identifier for the webhook event, can be used to prevent duplicate processing
Request body schema
Responses
Example Event