Skip to main content

Update a webhook endpoint

POST 
/api/v1/webhooks/update-endpoint

Reads the endpoint and overlays nonempty name, URL and description before sending the provider a replacement. Empty strings do not clear fields. There is no public revision precondition, so concurrent changes can overwrite one another.

The following access conditions are preserved as declared intent and are not implemented by generated code: Tenant request context, Tenant-scoped webhook ownership.

Use this in a guide: Recover a missing backend update · Receive a completed order summary in your backend

Request​

Responses​

Endpoint updated successfully

Update an existing endpoint after verifying the replacement receiver.​

Section ID: DOC-IN-webhooks-api-updateWebhookEndpoint#example-webhooks-updateWebhookEndpoint-request

Request example

{
  "endpointId": "ep_abc123",
  "url": "https://api.example.com/hooks/travila-v2"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.​

Section ID: DOC-IN-webhooks-api-updateWebhookEndpoint#example-webhooks-updateWebhookEndpoint-response

Response example

{
  "endpoint": {
    "id": "example_123",
    "name": "example",
    "url": "https://example.com/resource",
    "description": "example",
    "status": "ENDPOINT_STATUS_ACTIVE",
    "secret": "example",
    "httpTimeout": 1,
    "rateLimit": 1,
    "rateLimitDuration": "example",
    "createdAt": "2026-09-16T12:00:00Z",
    "updatedAt": "2026-09-16T12:00:00Z"
  }
}

Document ID: DOC-IN-webhooks-api-updateWebhookEndpoint. Section identities and revisions.

SectionStable reference
Update a webhook endpointDOC-IN-webhooks-api-updateWebhookEndpoint#overview
RequestDOC-IN-webhooks-api-updateWebhookEndpoint#request
ResponsesDOC-IN-webhooks-api-updateWebhookEndpoint#responses