Skip to main content
List webhook endpoints

Authorizations

Authorization
string
header
required

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

X-Request-Id
string

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.

Required string length: 1 - 128
Pattern: ^[A-Za-z0-9._-]+$
Example:

"req_01HZX3K9EXAMPLE"

Path Parameters

businessId
string<uuid>
required

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.

Pattern: ^[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}$
Example:

"018f3c4e-7b2a-7c3d-8e9f-0123456789ab"

Query Parameters

limit
integer
default:50

Maximum number of items to return (STD-API-01 D05). Default is 50 when omitted. Values greater than 200 must be rejected with 400.

Required range: 1 <= x <= 200
Example:

50

cursor
string

Opaque pagination cursor from a previous response pagination.next_cursor (STD-API-01 D05). Clients must not parse the cursor. Changing filter or sort parameters invalidates a previous cursor. Cursor lifetime is not set by this foundation and must be documented per capability when applicable.

Minimum string length: 1
Example:

"eyJvZmZzZXQiOiJleGFtcGxlIn0"

status
enum<string>

Endpoint lifecycle in v1 (DEC-WH-V01 deferred ownership verification; DEC-WH-E01 soft-delete). Endpoints become active after successful creation and destination security validation. disabled is the deactivated state after DELETE or explicit disable. Ownership verification is a future capability — not a v1 prerequisite.

Available options:
active,
disabled
Example:

"active"

Response

Endpoint page

Cursor-paginated webhook endpoints.

data
object[]
required

Page of resources. Item schemas are capability-specific.

pagination
object
required

Cursor pagination metadata for collection responses (STD-API-01 D05). Field names are normative: limit, has_more, next_cursor.

Example: