Job CreatedWebhook
Event broadcast when a job 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
Mapping coverage per connector
Example Event
Job UpdatedWebhook
Event broadcast when a job 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
Mapping coverage per connector
Example Event
Job DeletedWebhook
Event broadcast when a job 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
Applicant CreatedWebhookUpcoming
Event broadcast when an applicant 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
Mapping coverage per connector
Example Event
Applicant UpdatedWebhookUpcoming
Event broadcast when an applicant 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
Mapping coverage per connector
Example Event
Applicant DeletedWebhookUpcoming
Event broadcast when an applicant 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
Mapping coverage per connector
Example Event
Application UpdatedWebhook
Event broadcast when an application 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
Mapping coverage per connector
Example Event
Application DeletedWebhook
Event broadcast when an application 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
Application CreatedWebhook
Event broadcast when an application 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
Mapping coverage per connector
Example Event