Skip to Content
SeyloDocs
API referenceDeploy triggers and webhooks

Retry failed webhooks

POST
/api/v1/webhooks.redeliver

Asks GitHub to send failed deliveries for a service again (all failed ones from the last 3 days, or one). Each redelivery is handled like a new push.

Needs services.deploy on the service (a grant on its project covers it). Available to MCP clients and the assistant.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
serviceId*string

Panel-issued id.

Match^[a-z0-9]{16}$
deliveryId?string

Panel-issued id.

Match^[a-z0-9]{16}$

Response Body

Success.

application/json
  1. response
requested*integer
Range0 <= value
Example Request
curl -X POST 'https://example.com/api/v1/webhooks.redeliver' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string"}'
Example Response
{  "requested": 0}

List a service's webhook deliveries GET

Lists recent webhook deliveries (GitHub pushes and PR events, trigger URL calls) for a service, newest first, with what each one did and why. Needs `services.view` on the service (a grant on its project covers it). Available to MCP clients and the assistant.

Create or rotate a deploy trigger URL POST

Creates a new secret deploy URL for a service and invalidates the old one. A POST to the URL deploys the service (optional query: commit=<sha>). The URL is returned only this once. While the panel has no domain it is a path (/api/hooks/deploy/...) to put after the panel's address. Needs `services.update` on the service (a grant on its project covers it). Not available to MCP clients or the assistant.