Customer CreatedWebhook
Event broadcast when a customer 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
Customer UpdatedWebhook
Event broadcast when a customer 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
Customer DeletedWebhook
Event broadcast when a customer 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
Invoice CreatedWebhook
Event broadcast when an invoice 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
Invoice UpdatedWebhook
Event broadcast when an invoice 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
Invoice DeletedWebhook
Event broadcast when an invoice 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
Invoice Item CreatedWebhook
Event broadcast when an invoice has been item 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
Invoice Item UpdatedWebhook
Event broadcast when an invoice has been item 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
Invoice Item DeletedWebhook
Event broadcast when an invoice has been item 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
Ledger Account CreatedWebhook
Event broadcast when a ledger has been account 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
Ledger Account UpdatedWebhook
Event broadcast when a ledger has been account 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
Ledger Account DeletedWebhook
Event broadcast when a ledger has been account 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
Tax Rate CreatedWebhook
Event broadcast when a tax has been rate 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
Tax Rate UpdatedWebhook
Event broadcast when a tax has been rate 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
Tax Rate DeletedWebhook
Event broadcast when a tax has been rate 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
Purchase Order CreatedWebhook
Event broadcast when a purchase has been order 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
Purchase Order DeletedWebhook
Event broadcast when a purchase has been order 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
Purchase Order UpdatedWebhook
Event broadcast when a purchase has been order 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
Expense UpdatedWebhook
Event broadcast when an expense 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
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Expense DeletedWebhook
Event broadcast when an expense 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
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Expense CreatedWebhook
Event broadcast when an expense 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
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Quote DeletedWebhook
Event broadcast when a quote has been deleted.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Quote CreatedWebhook
Event broadcast when a quote has been created.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Quote UpdatedWebhook
Event broadcast when a quote has been updated.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Project UpdatedWebhook
Event broadcast when a project has been updated.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Project CreatedWebhook
Event broadcast when a project has been created.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event
Project DeletedWebhook
Event broadcast when a project has been deleted.
Request body schema
Unique reference to this request event
Name of Apideck Unified API
Service provider identifier
Unique consumer identifier. You can freely choose a consumer ID yourself. Most of the time, this is an ID of your internal data model that represents a user or account in your system (for example account:12345). If the consumer doesn't exist yet, Vault will upsert a consumer based on your ID.
The service provider's ID of the entity that triggered this event
The type entity that triggered this event
The url to retrieve entity detail.
The current count this request event has been attempted
ISO Datetime for when the original event occurred
Responses
Mapping coverage per connector
Example Event