Docs

Reference

Verify a receiver URL

Optional ownership check: sends webhook.verify with data.challenge; the receiver must answer 200 with {"challenge":"<value>"} within 10 s. Marks the webhook verified.

View MarkdownThis page is generated from the source code on every release.

Optional ownership check: sends webhook.verify with data.challenge; the receiver must answer 200 with {"challenge":"<value>"} within 10 s. Marks the webhook verified.

Overview

Name Value
Code webhooks.verify
Scope needed webhooks.manage
Risk Write
May need confirmation No
Runs as Answers right away
Needs Idempotency-Key No
Member roles allowed owner, manager, agent
In the app Settings → Webhooks

Input fields

Field Type Required Description
id uuid Yes

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/webhooks.verify \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":"00000000-0000-0000-0000-000000000000"}'

Output fields (data)

Field Type Required
delivery_id text Yes
webhook_id_header text Yes
delivered true/false Yes
status text Yes
status_code null | number Yes
duration_ms null | number Yes
error_code null | text Yes
error_text null | text Yes
response_snippet null | text Yes
key_ids text[] Yes
ok true Yes
verified true/false Yes
how text Yes

Example answer

{
  "data": {
    "delivery_id": "00000000-0000-4000-8000-000000000000",
    "webhook_id_header": "text",
    "delivered": true,
    "status": "text",
    "status_code": 1,
    "duration_ms": 1,
    "error_code": "text",
    "error_text": "text",
    "response_snippet": "text",
    "key_ids": [
      "text"
    ],
    "ok": true,
    "verified": true,
    "how": "text"
  }
}

Using it over MCP

Not listed on any profile: call tools_describe then tools_run with code: "webhooks.verify". Tool name when listed: webhooks_verify.

Was this page helpful?

Last checked: 10/24/2026 · build 2.0