[From Wrike] Wrike API v4 is now available ๐ฅ
Stephen
Thank you for your feedback! Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!
Folllowing List for Post: [From Wrike] Wrike API v4 is now available ๐ฅ
[this list is visible for admins and agents only]
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 ?
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 ๐
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 :)
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?
Hi Joris, speaking to my colleague I can see this was solved for you. If there's anything else, please let me know ๐
Thanks. The authorization errors were due to an user error, not the new API V4 token.
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?