Verify the configured receiver key and enable an endpoint

​

Sends a separate signed Standard Webhooks endpoint-key challenge to the registered HTTPS URL. Only a fresh challenge with a single matching response header and 2xx status enables this endpoint. Redirects, private destinations, DNS changes to private addresses and a concurrent endpoint revision change fail safely. An already enabled and verified endpoint returns its current receipt without another challenge. This response contains no signing key. Current application authority and admitted event producers still gate actual deliveries.

Path Parameters

Responses

  • application/json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
Request Example for post/v1/webhook-endpoints/{endpointId}/verifications
curl 'https://api.dev.eno.health/v1/webhook-endpoints/{endpointId}/verifications' \
  --request POST \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'
{
  "id": "string",
  "url": "https://example.com",
  "eventTypes": [
    "document.processed"
  ],
  "status": "disabled",
  "verificationStatus": "unverified",
  "revision": 1,
  "createdAt": "2026-11-16T18:04:16.401Z",
  "updatedAt": "2026-11-16T18:04:16.401Z"
}
Partner API reference · Check your integration’s enabled capabilities before making requests.