Wrike APIs now support expanded bulk API capabilities and a new asynchronous Batch API, enabling large-scale operations with significantly reduced rate-limit impact.

Bulk Update Enhancements

  • Tasks: Bulk update now supports parents, responsibles, responsible placeholders, and custom status (existing custom field and effort updates remain supported). See Tasks API .
  • Folders / Projects: Bulk update now supports project attributes including owners (add/remove), status, customStatusId, start and end dates, contract type, and budget (existing custom field updates and CIT conversion remain supported). See Folders & Projects API .

New Async Batch API

  • Introduced POST /batch for asynchronous bulk operations.
  • Submit up to 100 operations per request, counted as a single API call.
  • Currently supports TaskCreation and Folder Creation.
  • Supports heterogeneous batches within the same request.
  • Track execution and results using the async_job API.
  • Quota-Based Safeguards: Batch operations use a per-account operation quota that replenishes as operations complete, preventing resource starvation while supporting bursty automation workloads.
  • Documentation: Batch API documentation is now live: https://wrike.readme.io/wrike-production/reference/postbatchempty

Query lock periods for timelogs

Added https://wrike.readme.io/wrike-production/reference/getfolderssingletimelog_lock_periods. Query timelog lock periods for spaces, folders and tasks.


Create lock periods for timelogs (lock timelog periods)

Added https://wrike.readme.io/wrike-production/reference/postfolderssingletimelog_lock_periods. Create timelog lock periods for spaces, folders.


Delete lock periods for timelogs (unlock timelog periods)

Added https://wrike.readme.io/wrike-production/reference/deletefolderssingletimelog_lock_periods. Delete timelog lock periods for spaces, folders.


Support lockStatus, exportStatus in query timelog request/response

Modified https://wrike.readme.io/wrike-production/reference/gettimelogsempty. Added in fields element in request the option for exportStatus and lockStatus, to be able to be returned as info in response.


Wrike Webhooks now support granular event filtering and richer payloads for more efficient integrations.

  • Event Filtering — New parameterisedEvents and customItemTypes parameters let you receive webhooks only for specific events (e.g., when a particular CF changes).
  • Customizable Payloads — Use the fields parameter to include extra contextual data (e.g., title, status, project, customFields etc.) directly in the webhook payload.

Learn more about the enhancements →

GET /audit_log

The GET /audit_log now supports filtering by userId, objectType, and objectId for more targeted access to relevant audit log entries.

GET /spaces

The GET /spaces now supports filtering by title & accessTypes helping you narrow down results by personal, private, public, or locked spaces.

GET Folder-related endpoints

The GET /folders, GET /folders/{folderId}/folders & GET /spaces/{spaceId}/folders now support filtering by authors, owners, title, customStatuses. These filters enable more precise folder retrieval based on ownership, naming, or custom workflow statuses.

We’re excited to announce the launch of OpenAPI Specification & [New] Schema Reference for Wrike’s Public APIs.

You can now access it under API reference v4 > [New] Schema Reference

What’s New?

While the API endpoints and functionality remain unchanged, the new schema unlocks several powerful benefits:

  • Downloadable OpenAPI Spec: Get the full OpenAPI specification to explore and integrate Wrike APIs using your favorite tools.
  • In-browser Try it out option: Quickly test endpoints directly from your browser without switching platforms.

No Functional Changes

This update does not introduce any new API endpoints or breaking changes. It simply makes the existing methods available in a widely adopted and developer-friendly format.

Deprecation Notice

Going forward, the [New] Schema Reference page will serve as the primary source for all Wrike public APIs. We recommend starting using this update to ensure continuity and take advantage of improved usability.

The existing API reference v4 > Methods pages will be deprecated by August 31st, 2025 and will no longer receive updates.