Activity CreatedWebhook
Event broadcast when an activity 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
Activity UpdatedWebhook
Event broadcast when an activity 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
Activity DeletedWebhook
Event broadcast when an activity 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
Company CreatedWebhook
Event broadcast when a company 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
Company UpdatedWebhook
Event broadcast when a company 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
Company DeletedWebhook
Event broadcast when a company 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
Contact CreatedWebhook
Event broadcast when a contact 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
Contact UpdatedWebhook
Event broadcast when a contact 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
Contact DeletedWebhook
Event broadcast when a contact 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
Lead CreatedWebhook
Event broadcast when a lead 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
Lead UpdatedWebhook
Event broadcast when a lead 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
Lead DeletedWebhook
Event broadcast when a lead 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
Note CreatedWebhook
Event broadcast when a note 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
Note UpdatedWebhook
Event broadcast when a note 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
Note DeletedWebhook
Event broadcast when a note 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
Opportunity CreatedWebhook
Event broadcast when an opportunity 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
Opportunity UpdatedWebhook
Event broadcast when an opportunity 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
Opportunity DeletedWebhook
Event broadcast when an opportunity 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