curl --request GET \
--url https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)HttpResponse<String> response = Unirest.get("https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}")
.header("Authorization", "Bearer <token>")
.asString();{
"id": "018f3c4e-7b2a-7c3d-8e9f-ffffffffffff",
"type": "sms.message.delivered.v1",
"created_at": "2026-10-13T09:00:05.000Z",
"business_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789ab",
"api_version": "v1",
"data": {
"message_id": "018f3c4e-7b2a-7c3d-8e9f-aaaaaaaaaaaa"
}
}Retrieve a webhook event
Single event envelope. Does not expose delivery secrets or internal routing.
curl --request GET \
--url https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId} \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)HttpResponse<String> response = Unirest.get("https://api.1-funnel.org/v1/businesses/{businessId}/webhook-events/{eventId}")
.header("Authorization", "Bearer <token>")
.asString();{
"id": "018f3c4e-7b2a-7c3d-8e9f-ffffffffffff",
"type": "sms.message.delivered.v1",
"created_at": "2026-10-13T09:00:05.000Z",
"business_id": "018f3c4e-7b2a-7c3d-8e9f-0123456789ab",
"api_version": "v1",
"data": {
"message_id": "018f3c4e-7b2a-7c3d-8e9f-aaaaaaaaaaaa"
}
}Authorizations
OAuth 2.0 Client Credentials for the External Integration API (ADR-015, ADR-023).
Client authentication: HTTP Basic (client_secret_basic).
Access-token audience: 1funnel-external-api.
The tokenUrl below is the production target. Sandbox uses a different
host. OpenAPI cannot bind tokenUrl to the selected servers entry; see
x-1funnel-oauth on the root document and the authentication guide when published.
Coarse OAuth scopes (if any) are token-level vocabulary (ADR-013 IA-06). They
are not the ADR-022 resource permission catalogue. Resource permissions
are enforced after token validation via application-to-business grants
(ADR-016) and are documented per operation with x-required-permissions.
These URLs are architecture targets. They are not claimed to be deployed or generally available.
Headers
Request correlation identifier (STD-API-01 D12). Clients may supply a value
of 1–128 characters matching A-Za-z0-9._-. Missing or invalid values are
replaced by a server-generated identifier. Distinct from W3C traceparent,
resource ids, Idempotency-Key, and webhook event ids.
1 - 128^[A-Za-z0-9._-]+$"req_01HZX3K9EXAMPLE"
Path Parameters
Business resource selector in /v1/businesses/{businessId}/… (ADR-006).
UUIDv7-compatible opaque identifier. {businessId} is not authorization
proof. The resource server must independently verify an active
application-to-business grant, required permission, and ownership (ADR-016,
ADR-022).
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Webhook event identifier (UUIDv7). Distinct from delivery and attempt ids.
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Response
Event detail
CloudEvents-inspired management-view envelope (ADR-021 WH-03 / ADR-017
SECOP-10 / DEC-ASYNC-ENV-01). Not a claim of full CloudEvents compliance.
Event-specific data payload schemas are defined in the AsyncAPI contract
(asyncapi/external-integration-webhooks/). This OpenAPI view keeps data
as an object so management reads stay compatible with additive AsyncAPI
payload evolution (DEC-ASYNC-COMPAT-01).
Stable logical event id. Retries preserve this id.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Approved v1 outbound event types (ADR-021 WH-02). Wallet and payment events are deferred. Do not rename these values.
sms.message.sent.v1, sms.message.delivered.v1, sms.message.failed.v1, sms.bulk-message.processing.v1, sms.bulk-message.completed.v1, sms.bulk-message.failed.v1, otp.challenge.verified.v1, otp.challenge.expired.v1, otp.challenge.locked.v1 "sms.message.delivered.v1"
RFC 3339 date-time. Response timestamps are UTC with a Z offset
(STD-API-01 D06). Client-supplied timestamps must include an explicit offset;
local times without an offset are rejected.
"2026-10-13T09:00:00.000Z"
UUID with version nibble 7 (UUIDv7). STD-API-01 prefers UUIDv7 for new
platform-generated external resource identifiers. Clients must still treat
the value as opaque. Not every path parameter is guaranteed to be v7 solely
because it is a UUID; use this schema where the contract asserts UUIDv7.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-7[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"
Webhook event envelope API version (DEC-ASYNC-ENV-02). Constant v1.
Distinct from REST path prefixes and from the event-type suffix (.v1).
"v1""v1"
Minimal event data. Typed payloads are defined in AsyncAPI (ADR-011 / ADR-021). Consumers must tolerate additive fields.