Stephen

October 05, 2018 09:43

[From Wrike] Wrike API v4 is now available 🔥

Follow

We are happy to announce the immediate availability of Wrike API v4. Our flexible work management platform allows you to integrate with your existing tools and systems with Wrike. API v4 is a new generation of REST APIs that is designed for improved security and scalability. Learn more here.

 

The primary difference between Wrike API v4 and v3 is that the new version can only access data from one account at the time, and the method URIs are changed accordingly. Although they're very similar, API v4 and v3 are incompatible and some changes in calling code might be required. The full migration guide is available here.

 

In order to complete improvements for Wrike security and scalability, we will be deprecating Wrike API v3 in favor of new version. End of Life of API v3 is June 30th, 2019 and API calls are not guaranteed to work after that date.

 

We are happy to help with migration and will answer all questions on Developer Community, comment below 👍

• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Thuy Dung Nguyen

  October 12, 2018 10:24

  Hello, I follow the official documentation on v4 api but it's impossile to access. For example:

  If I call v4 in the browser with "https://www.wrike.com/api/v4/folders" I get a 500 error

  If I change to "https://www.wrike.com/api/v3/folders" I get the data.

  Can you tell me if I did something wrong while calling v4 ?

  Is this helpful? 0

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Stephen

  October 24, 2018 10:24

  Hi Thuy, for security reasons, new APIv4 do not support direct requests at your browser anymore. So you can not request "https://www.wrike.com/api/v4/folders" without "Authorization: bearer" otherwise the server will return an error.

  The correct example will be:
  curl -g -X GET -H 'Authorization: bearer <access_token>' 'https://www.wrike.com/api/v4/folders' 
  More information can be found at https://developers.wrike.com/documentation/api/methods/get-folder-tree

   

  Let me know if you need further help and I can raise a ticket to our Support Team to help 🙂

  Is this helpful? 0

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  John Dexter

  November 07, 2018 12:08

  I'm new to Wrike and hadn't realised there was an API - I'm very pleased to hear there is. We use Wrike to integrate with GitHub - can you suggest any good examples how the API might be useful to us, any good use-cases rather than just the API docs?

   

  Thanks :)

  Is this helpful? 0

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Joris Hoffbauer

  December 01, 2018 07:55

  Hi,

  As someone with no developer or programmer background, this article on connecting Wrike's API with MS Excel has been extremely useful to me. However, I'm getting authorization errors if I try to follow the steps with a new API v4 Token and V4 request URIs.

  Would it be possible to update this guide to include all steps needed for Wrike API v4?

  Is this helpful? 0

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Stephen

  January 04, 2019 15:08

  Hi Joris, speaking to my colleague I can see this was solved for you. If there's anything else, please let me know 👍

  Is this helpful? 1

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Joris Hoffbauer

  January 07, 2019 15:30

  Thanks. The authorization errors were due to an user error, not the new API V4 token.

  Is this helpful? 0

  Comment actions Permalink
• Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪

  

  Zeev Tarantov

  April 21, 2019 13:46

  a POST to https://www.wrike.com/oauth2/convert_v3_token results in 
  
  < HTTP/2 500
  < server: nginx
  < date: Sun, 21 Apr 2019 13:39:15 GMT
  < content-type: application/json;charset=UTF-8
  < content-length: 59
  < wrike-response-id: 46eaa7d54a3ae7f
  < pragma: no-cache
  < cache-control: no-cache
  < x-xss-protection: 1; mode=block
  < x-content-type-options: nosniff
  < strict-transport-security: max-age=31536000; includeSubDomains; preload
  <
  * Connection #0 to host www.wrike.com left intact
  {"error":"server_error","error_description":"Server error"}
  
  Even if I'm submitting the data wrong, I expect to get HTTP 4xx, not 500. Is this a temporary thing that is expected to get fixed very soon, or is this the expected behavior of the API for now?

  Is this helpful? 0

  Comment actions Permalink

Please sign in to leave a comment.