List All Webhooks
Changed onView all webhooks associated with a specific company with filtering available via query parameters.
OAuth Scope required: public.webhooks.readWebhooks
Request
- Base URLhttps://ironcladapp.com/public/api/v1
- URLhttps://ironcladapp.com/public/api/v1/webhooks
- AuthAPI key in header Authorization and OAuth 2Authorization code: https://ironcladapp.com/oauth/authorizeClient credentialsToken URL: https://ironcladapp.com/oauth/token scopes: public.webhooks.readWebhooks
Query parameters
The page number used when paginating through a list of results.
A limit of the number of results to return.
Headers
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-id is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Denotes the actor of the request. When used, the API will take into account this user's permissions and access. This or x-as-user-email is required when the associated token was produced from the Client Credentials grant or with legacy bearer tokens on select endpoints. A token produced from the Authorization Code grant (which is already scoped to a user) may also use this header to act as a different user in the same company, provided the token carries the identity.users.impersonate scope and the token's own user has been granted the API User Impersonation permission. A request that sends this header without both never acts as the named user; depending on the company's configuration it either proceeds as the token's own user or is rejected with a 403. More information about permissions.
Response
200
Example response
{
"pageSize": 20,
"list": [
{
"id": "5928719b30182d3700364a74",
"events": [
"workflow_launched"
],
"targetURL": "https://develop.ironcladapp.com",
"companyId": "5928719b30182d3700364a74",
"status": "enabled",
"statusLastUpdatedAt": "2025-01-17T17:51:49.008Z",
"statusLastUpdatedBy": "system",
"firstConsecutiveFailure": "2025-01-17T17:51:49.008Z"
}
]
}Changes
- warning
added the new
workflow_deletedenum value to the///response property for the response status
- warning