A guide for managing webhooks in the UI.
Entity | Event Types | Description | Method & Payload |
---|---|---|---|
Label | LABEL_CREATED, LABEL_UPDATED, LABEL_DELETED | Triggers when labels have been created, updated, or deleted. | HTTP POST |
Model run training | Created (HTTP POST) | Triggers when training of a model run has been initiated Note this webhook does not yet conform to standard webhook subscriptions. It must be registered in the Model User Interface. | HTTP POST |
Models list | Queries (HTTP GET) | Callback to retrieve a list of model types for a given model training backend | HTTP GET |
Workflow | MOVE | Triggers when a workflow action happens, e.g. after a data row was approved or rejected during a review step, or after it was manually moved to a different queue. | HTTP POST |
What is the outgoing rate for webhooks?
Is there an upper limit on the size of the webhook payload?
Does Labelbox use any non-https connections to send webhook events?
Is the Content-Type header from the labelbox webhook events only “application/json”?
What is the first `id` in the payload for label-related events?
Is the order of events from a Labelbox webhook guaranteed to be the same as the order in which the label/review was created/updated/deleted?