Wrike API v4
This document covers the methods and techniques required to access and modify user content in Wrike through the API.
Wrike’s API uses the OAuth 2.0 protocol for authorization. Every API request must contain the Authorization header (preferred option) or the access_token parameter with the OAuth 2.0 access token. Access scopes may be requested during the authorization process. See the OAuth 2.0 authorization description for details.
The API methods are organized in the RESTful way and support GET, POST, PUT and DELETE requests. If a client is not able to execute all kinds of requests, then only GET requests can be used with an additional method parameter, which is set to the required request type (e.g., ...&method=POST).
To access a specific API method, the request token should have at least one of the scopes required by this method. Supported scopes: Default, wsReadOnly, wsReadWrite, amReadOnlyWorkflow, amReadWriteWorkflow, amReadOnlyInvitation, amReadWriteInvitation, amReadOnlyGroup, amReadWriteGroup, amReadOnlyUser, amReadWriteUser.
Each API method operates on a certain type of resource with a defined model (for details, see the Methods section below) and produces a JSON response that contains the entity type in the kind field and an array of entities in the data field. Client can pass an additional state parameter in the request, which also will be included in the response.