cURL
curl --request GET \
--url https://api.slash.com/webhook/{webhookId} \
--header 'X-API-Key: <api-key>'{
"id": "<string>",
"createdAt": "<string>",
"url": "<string>",
"name": "<string>",
"archivedAt": "<string>",
"pausedAt": "<string>",
"backingOffUntil": "<string>",
"disabledAt": "<string>"
}Webhooks
Get webhook
Get a webhook endpoint by ID
GET
/
webhook
/
{webhookId}
cURL
curl --request GET \
--url https://api.slash.com/webhook/{webhookId} \
--header 'X-API-Key: <api-key>'{
"id": "<string>",
"createdAt": "<string>",
"url": "<string>",
"name": "<string>",
"archivedAt": "<string>",
"pausedAt": "<string>",
"backingOffUntil": "<string>",
"disabledAt": "<string>"
}Authorizations
api_keybearer
API key authentication for public API requests.
Keys come in two flavors:
- Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
- User-scoped keys are pinned to a user and span every legal
entity that user has access to. Every request made with a
user-scoped key (except
GET /legal-entity, which lists the legal entities the user can access) must include anx-legal-entityheader naming the legal entity the request is operating on. Requests without the header are rejected with400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with403.
Path Parameters
Response
OK
The URL that will receive the webhook payload
The name of the webhook
The current status of the webhook endpoint:
active: The webhook is enabled and receiving events normally.paused: The webhook has been paused by the user. Events are queued and will be delivered when the endpoint is set back toactive.backing-off: The system is temporarily backing off due to delivery failures. Delivery will be automatically retried atbackingOffUntil. You can also immediately re-enable by setting status toactivevia the PATCH endpoint.disabled: The webhook has been automatically disabled due to repeated delivery failures. Re-enable by setting status toactivevia the PATCH endpoint.
Available options:
active, paused, backing-off, disabled When the endpoint was paused by the user (ISO 8601 timestamp)
When the system will automatically retry delivery (ISO 8601 timestamp). Only present when status is backing-off.
When the endpoint was automatically disabled due to repeated failures (ISO 8601 timestamp). Only present when status is disabled.
⌘I