Project webhook routes
Use the project-prefixed aliases for webhook configuration and logs.
Paths
These routes expose the same operations as the environment-scoped /v1/webhooks endpoints:
| Method | Path | Operation |
|---|---|---|
| POST | /v1/projects/{projectId}/webhooks | Create a webhook |
| GET | /v1/projects/{projectId}/webhooks | List webhooks |
| GET | /v1/projects/{projectId}/webhooks/{endpointId} | Read a webhook |
| PATCH | /v1/projects/{projectId}/webhooks/{endpointId} | Update a webhook |
| DELETE | /v1/projects/{projectId}/webhooks/{endpointId} | Remove a webhook |
| POST | /v1/projects/{projectId}/webhooks/{endpointId}/rotate-secret | Rotate the signing secret |
| GET | /v1/projects/{projectId}/webhooks/signature-contract | Read signing and retry policy |
| GET | /v1/projects/{projectId}/webhooks/{endpointId}/deliveries | List webhook deliveries |
| GET | /v1/projects/{projectId}/webhooks/{endpointId}/deliveries/{deliveryId} | Read a webhook delivery |
| POST | /v1/projects/{projectId}/webhooks/{endpointId}/deliveries/{deliveryId}/replay | Replay a webhook delivery |
Scope
Pass projectId in the path. With a secret API key, projectId must match the key and environmentId defaults to its environment.
With a console session, supply environmentId in the query and belong to the project's organization.
Authentication
Secret keys require webhooks:read for reads or webhooks:write for writes. Console-session writes require the owner or admin role and an Origin header matching the trusted console origin.
Example
curl "$RELAYRTC_API_URL/projects/project_example/webhooks?environmentId=environment_example" \
-H "Authorization: Bearer $RELAYRTC_SECRET_KEY"Request and response fields
Follow the linked operation pages. The Node SDK uses the shorter /v1/webhooks endpoints.