MONDAY, MARCH 30, 2015
Custom Statuses and Workflows

Today we announced the release of Custom Workflows, where users are no longer confined to the four default task statuses (read all the details in this blog post). Custom Statuses and Custom Workflows operations are already available through the API:

We have also added auth scopes related to managing Workflows (read the details on auth scopes in our docs on OAuth):

  • amReadOnlyWorkflow, amReadWriteWorkflow: access to the Workflow endpoints is given only for apps that request these scopes during authorization. Access is either read-only or read/write, respectively.
  • amReadOnlyWorkflow has also been added to the default auth scope, so by default users can retrieve a list of all existing Workflows in the account.

We have also updated the Custom Fields parameter returned in [GET] /accounts: now you will know the type of Custom Field and can handle data input / output correctly, whether it is a boolean value, date, or any other type of data supported in Custom Fields.

MONDAY, MARCH 2, 2015
API Auth Scopes

We have added auth scopes that express Wrike data user permissions. The scope is selected during the OAuth 2.0 authorization (details in our docs on OAuth). Possible values are the following:

  • wsReadOnly, wsReadWrite: required for requests involving all data available to users in the Wrike workspace (tasks, folders, comments, timelogs, etc.). Access is either read-only or read/write, respectively.
  • amReadOnlyInvitation, amReadWriteInvitation: invitation related requests. Access is either read-only or read/write, respectively.

If no scope is explicitly requested, we set the default scope to the API client, which is equal to wsReadWrite. This means that by default, users interacting with Wrike through the API can modify any data available to them in the Wrike accounts they have access to, except user invitations.

Monday, February 9, 2015
New and Deprecated Parameters

Here's some info about upcoming updates to the Wrike API 3.0.

The following updates will be released on February 19, and may affect your applications as some minor API features will be deprecated:

1. In [GET] /folders methods:

  • children member will be deprecated. Instead, please use childIds, which was introduced in October 2014. Check docs

2. In /timelogs methods:

  • date parameter will be deprecated. Instead, trackedDate should be used.
  • date member will be deprecated. Instead, createdDate or trackedDate should be used, depending on your purpose.

These new features are being released on February 17 to help you improve your workflow:

1. [GET] /tasks methods were updated with several parameters:

  • Subtasks can now be included in the search scope: e.g. /tasks?subTasks=true
  • Values of custom fields and also their general availability for a task can now be included in the search scope: e.g. /tasks?customField={id: "search_id", value: "optional_search_value"}

2. [GET] /folders methods have been updated with search by permalink: e.g. /folders?permalink=...

3. Optional field briefDescription has been added to Folder model.

4. For those who are migrating their apps from APIv2 we now provide the [GET] /ids method, which can be used to convert legacy APIv2 IDs into APIv3 IDs.

Monday, 15 December, 2014
Custom fields and metadata

Today we announced our Dynamic Platform Release and there's a long list of things we've been up to in the last couple of months (see our blog post). But the highlight of the release is Custom Fields. Now every task can contain properties you and your coworkers create according to your own needs. This feature is already reflected in the API in the following way:

  • You can get a full list of Custom Fields created in your account using [GET]/accounts
  • You can read and edit values of Custom Fields on specific tasks using [GET]/tasks and [PUT]/tasks

Don't forget that visibility of Custom Fields values is set on a per-user basis. Search of tasks by Custom Field names and values is on the way!

Still, Custom Fields is kind of a user interface oriented feature and of course there is some data which does not need to be visible. So we're also releasing an API-exclusive Metadata feature. Now all your Accounts, Users, Folders, and Tasks can be updated with metadata — for instance, mappings with IDs of objects in other tools and systems you use. Metadata is isolated on a per-application basis and can be accessed through methods working with aforementioned Object types. Check the full API reference for more info.

Monday, 24 November, 2014
Limits on text fields

We've added a couple of limits for text fields which you change through API, here's the list:

  • Task and Folder Titles - 1,000 characters
  • Task description - 1,000,000 characters
  • Task and Timelog Comments - 10,000 characters
Monday, 20 October, 2014
Task dependencies, easier folder tree traversal and checks on modifying deleted entries

We've added several new features into our API and made slight modifications to existing methods to make interactions more convenient and logical.

First of all, we now support a feature that was previously accessible only through the web-interface: task dependencies. They are mostly used on our own Timeline view (Gantt chart) but now you can make a similar representation. Dependencies are not part of a Task model but a separate entity with its own group of methods - check the Dependencies reference.

In order to facilitate folder tree traversal we've done the following:

Also we now strictly forbid modification operations with entries which are children of deleted entries or deleted entries themselves, e.g.:

  • Create/modify comment in deleted task
  • Create/modify timelog in deleted task
  • Add/modify attachment in deleted task
  • Modify deleted task itself
Great companies rely on Wrike