Source
Integrations — found from sitemap — Wrike
Checked for Wrike on 1 Oct 2026
- Page
- https://developers.wrike.com/docs/webhooks
- Checked
- 1 Oct 2026, 15:59 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:6cf58540fd1c0bb281f26229b3122405e6320cc17928f5939491ba3c5b16e342
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Webhooks scopes Report an error
“We support the following scopes for webhooks: Folder webhooks - Fire notifications about changes to tasks, folders, projects within a single folder or project.”
-
Webhooks recursive Report an error
“recursive (optional) - Specifies whether hook should listen to events for subfolders and subprojects anywhere in the hierarchy. Default value is false, set to true for tracking all nested elements.”
-
Webhooks account endpoint Report an error
“[POST] /webhooks — Creates a webhook for a current account.”
-
Webhooks folder endpoint Report an error
“[POST] /folders/{folderId}/webhooks — Creates a webhook for a target folder/project.”
-
Webhooks space endpoint Report an error
“[POST] /spaces/{spaceId}/webhooks — Creates a webhook for a target space.”
-
Webhooks secret parameter Report an error
“secret (optional) - Client secret to check authenticity of the events later. See Secure Webhooks section below.”
-
Webhooks crud API Report an error
“REST-style API methods allow you to create webhooks, get lists of your webhooks and their states, update webhook states, and delete webhooks.”
-
Webhooks filtering Report an error
“Wrike webhooks now support advanced filtering via parameterisedEvents and customItemTypes parameters and customizable payloads via the fields parameter in parameterisedEvents, allowing you to be more selective about the events you receive and include additional context directly in the payload.”
-
Webhooks filter events Report an error
“TaskCreated recurrent true (only recurrent task), false (only non-recurrent task)”
-
Webhooks cit filter Report an error
“Use the customItemTypes parameter when creating the webhook to receive notifications for all supported events, but only for tasks or projects that belong to the specified CITs.”
-
Webhooks payload fields Report an error
“Request extra fields inline when a parameterisedEvents entry fires by adding a fields array to that entry. Returned fields appear under top-level fields in the webhook payload. This avoids extra API calls to fetch contextual data.”
-
Webhook delivery ips Report an error
“For US DC: 160.19.162.0/23, 34.73.3.211/32 For US2 DC: 35.196.104.95/32, 34.72.158.28/32 For EU DC: 185.157.64.0/22, 146.148.2.222/32”
-
Webhook signing Report an error
“Wrike optionally supports signing event payloads with a secret, pre-shared between client and Wrike. This provides a mechanism to check authenticity of the request”
-
Webhook event categories Report an error
“Events on tasks, folders, projects, attachments, timelogs, and comments changes are supported. Folder events are also fired on projects.”
-
Webhook get limit Report an error
“[GET] /webhooks/{webhookId},{webhookId},... [up to 100 IDs] — Returns information for the specified webhooks.”
8 facts read from this page are not shown because they could not be confirmed on the page as captured.