Create a new webhook-endpoint.
Security: OAuth 2.0
The Lucca API implements the oAuth 2 protocol with the client-credentials-flow. Refer to RFC8725.
Only execute the request if current cached version of the resource does not match the one given here.
"W/q5sd4w2x1c1gfdg"
Only execute the request if current cached version of the resource matches the one given here. Useful to avoid concurrency conflicts.
"W/q5sd4w2x1c1gfdg"
List of compression algorithms you support.
Include metadata:
embedded
: the partial or complete representations of related resources
(e.g. the employee the resource belongs to).links
: links to related resources or actions (e.g. approving a leave-request).
May be null
when you do not have access to the resource (or action).totalCount
: only applicable on collections (i.e. lists of resources), gives
the total number of items across all pages.Read more about expanding responses.
Representation of a webhook-endpoint
A webhook-endpoint describes the endpoint on your side that will receive events from your Lucca account.
It must handle HTTPS and support POST requests.
It should always check the signature of received events in order to increase security.
It should respond as fast as possible, otherwise, the server may stop sending it events.
Please refer to the webhooks documentation to learn more about webhook-endpoints. The webhook-endpoint to create.
Created
A webhook-endpoint describes the endpoint on your side that will receive events from your Lucca account.
It must handle HTTPS and support POST requests.
It should always check the signature of received events in order to increase security.
It should respond as fast as possible, otherwise, the server may stop sending it events.
Please refer to the webhooks documentation to learn more about webhook-endpoints. The created webhook-endpoint resource.