Skip to main content
POST
Create org webhook

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Headers

Trio-Version
enum<string>
required

Version of the v2 contract the client is written against. Each breaking change publishes a new version.

Available options:
2026-10-19.v2
Trio-Target-Org-Id
string<uuid>

ID of another org to act on instead of the API key's own org. The key's org must have been granted access to it, and the request is refused with 403 FORBIDDEN otherwise. When that access or the API key is read-only, only GET and HEAD requests may carry it. When the target org requires mTLS, so does the request. Leave it out to act on the key's own org.

Body

application/json

Org webhook parameters

Webhook to create. A url_secret webhook needs notification_url and notification_secret; an oauth webhook needs oauth_client_id, oauth_client_secret, oauth_url and oauth_scope.

authentication_method
enum<string>
required

How Trio authenticates to the notification URL

Available options:
url_secret,
oauth
notification_url
string
required

URL the events are sent to

api_version
enum<string> | null

Version of the event payloads sent to the webhook. Defaults to v100

Available options:
v100,
v200
entity_id
string<uuid> | null

Entity to limit the webhook to

event_categories_allowed
object[] | null

Events to send to the webhook. Empty or null sends every event

group_id
string<uuid> | null

Group of the entity to limit the webhook to

notification_secret
string | null

Secret sent with every event, for url_secret webhooks

oauth_client_id
string | null

OAuth client ID

oauth_client_secret
string | null

OAuth client secret

oauth_scope
string | null

OAuth scope

oauth_url
string | null

OAuth token URL

Response

Created webhook

A webhook the org receives its events at

data
V2 Org webhook · object

A webhook the org receives its events at

Example: