Webhook Custom Template Overview
Service Type
A service refers to a third-party application service, typically based on an HTTP server. Currently, Leiga primarily supports the following service types: Leiga service, which is suitable for personalized customization and development by users.
Event Type
An event refers to information generated by the system itself or user operations that trigger events. Events include relevant business data and basic event information. Currently, Leiga supports the following events:
Work
Create Work
Update Work
Delete Work
Comment
Add Comment
Update Comment
Delete Comment
Attachment
Upload Attachment
Delete Attachment
Subtask
Add Subtask
Update Subtask
Delete Subtask
Linked Work
Add Linked Work
Delete Linked Work
Sprint
Create Sprint
Start / Restart Sprint
Complete Sprint
Delete Sprint
The data content of events varies depending on the type of event. Please refer to the following data structure: Webhook Custom Template Variables
Leiga Custom JSON Template:
Currently, the system does not support custom template configuration options in Leiga format. All messages will be sent using the following template:
Request data example:
Leiga Service Description
Request Method: POST
Request Header
Header | Description | |
---|---|---|
X-Leiga-Event | Event identifier. The format is "object.action" | - |
Object | Description | |
Issue | Work | |
Comment | Comment | |
Attachment | Attachment | |
Subtask | Subtask | |
RelationIssue | Linked Work | |
LIA | Automation | |
Webhook | Webhook | |
Action | Description | |
Create | Create | |
Update | Update | |
Start | Start: Often paired with the object Sprint to signify the initiation or resumption of an sprint. | |
Complete | Complete: Commonly utilized with the object Sprint to denote the end or completion of an sprint. | |
Delete | Delete | |
Action | Operation. Usually used together with the object Automation, indicating automation operation. | |
Test | Test. Typically used with object Webhooks to indicate a test operation of the webhook. | |
X-Leiga-WebHook-ID | Unique identifier for the configured webhook | - |
X-Leiga-Type | Format of the request | - |
Format | Description | |
Leiga | Leiga Service | |
X-Leiga-Ts | Timestamp of the request (in seconds) | - |
X-Leiga-ID | Unique identifier for the request to identify a specific occurrence | - |
X-Leiga-Retry-Num | Retry number. Initially set as 0 and incremented for each subsequent request | - |
X-Leiga-Token | Token for the webhook configuration | - |
X-Leiga-Sign | Data signature string (currently not supported) | - |
Request body data format:
application/json; charset=utf-8
. Default data format example:
Response requirements after receiving a webhook:
After receiving an HTTP POST request, the application needs to respond to the request within 3 seconds with an HTTP 200 status code and the following JSON response body. Otherwise, this push will be considered a failure, and in the WebHooks-Send Records corresponding to the webhook, this request will be recorded as a failed request.
Timeout Description:
Connection timeout: 3 seconds, request timeout: 3 seconds, total: 6 seconds.
Appendix 1: Template Variables
Last updated