OriginChainDB
Database endpoints

Read a webhook

Read a webhook's configuration. The signing-secret setting is named, but its value is not returned.

GET /v1/tenants/{tenant}/webhooks/{hook_id}

Inspect how a webhook maps incoming dataThe signing-secret setting is named without exposing its value.
  1. Select the registered hookUse the webhook ID.
  2. Read its saved configurationInspect destination schema and field mappings.
  3. Check signature settingsSee how deliveries are verified without reading the secret.

Before you start

Use your database bearer token.

Connection setup

Use the registered hook's ID. This request returns the secret setting's name, not the secret value.

Path parameters

FieldTypeRequired
tenantstringRequired
hook_idstringRequired

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Read the result

Read the destination schema and field mappings to see how payloads become rows. The response names the signing-secret environment variable without exposing its value.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
404Check the resource ID and API route.
429Honor Retry-After when present; back off.
500Check the outcome before retrying a write.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd