Escalation destination
Get the destination of the escalated cases
Where the cases escalated to the technical team go: a Linear team or a webhook URL. It also returns the callback URL where the other tool reports the answer. API keys and signing secrets are never returned. 404 when no destination is connected. Read only and safe to repeat.
Required scope: escalation-destination:read.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Get the destination of the escalated cases › Responses
objectidproviderThe secrets Lelemon generated in this call. They are shown once, here, and never again: save them now. null when nothing new was generated, and always null on reads.
createdAtupdatedAtConnect the destination of the escalated cases
One destination per organization; connecting again replaces it. With provider linear, Lelemon checks the API key and the team with Linear, creates the webhook in Linear by itself (resource Issue, that team, signing secret generated by Lelemon) and deletes the one it created before when the team changes. If the key belongs to someone who cannot create webhooks in Linear, the destination is saved anyway with callback.registration manual: register callback.url in Linear and send its signing secret in linear.webhookSecret. With provider webhook, Lelemon posts a signed JSON to your https URL for each escalation and generates two secrets, returned once in secrets: one signs what Lelemon sends, the other signs what your tool sends back to callback.url. Changing from one provider to another deletes the Linear webhook Lelemon had created. 422 escalation_destination_rejected when the data is not accepted; 503 when Linear does not answer. Safe to repeat.
Required scope: escalation-destination:write.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Connect the destination of the escalated cases › Request Body
providerlinear: Lelemon creates the task in Linear and registers the webhook there. webhook: Lelemon posts a signed JSON to your URL, which covers Jira, Trello, n8n, Zapier or any tool.
Required when provider is linear.
Required when provider is webhook.
Connect the destination of the escalated cases › Responses
objectidproviderThe secrets Lelemon generated in this call. They are shown once, here, and never again: save them now. null when nothing new was generated, and always null on reads.
createdAtupdatedAtDisconnect the destination of the escalated cases
Deletes the destination with its keys and secrets, deletes the webhook Lelemon created in Linear, and stops accepting callbacks. The tasks already created stay in the other tool and the escalations stay in the cases. 503 when Linear does not answer, and then nothing is deleted so you can repeat the call. Repeating the call after it worked returns 404.
Required scope: escalation-destination:write.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Disconnect the destination of the escalated cases › Responses
List the Linear teams and projects a key can see
Use it before connecting Linear to choose the team and the project. The key is used once and not stored. 422 escalation_destination_rejected when Linear does not accept the key; 503 when Linear does not answer. Read only and safe to repeat.
Required scope: escalation-destination:write.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Idempotency-KeyMakes the request safe to retry. Once it starts running, its final response (2xx, 4xx or 5xx) is kept for 24 hours and the same key gets it back, without repeating the effect. A request rejected before it runs leaves the key free. A replayed create omits the secret. The same key with a different request is rejected with 409 idempotency_key_reused.
List the Linear teams and projects a key can see › Request Body
apiKey^\S+$ · requiredA Linear personal API key. It is used once and not stored.
List the Linear teams and projects a key can see › Responses
objectList the latest escalations of the organization
The escalations of all the cases to the technical team, newest first, with their status and the task in the other tool. Read only and safe to repeat.
Required scope: escalation-destination:read.
query Parameters
limitcursorThe nextCursor of the previous page, with the same filters.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
List the latest escalations of the organization › Responses
objecthasMorenextCursor