Wrike Task IDs vs API Ids

I am curious about why the Task IDs you get from a URL Query differs than the ID that is needed for the API.

An example is if I want to pull a Task ID it will have two different IDS:

URL: wrike.com/workspace.htm?path=folder&id=1234
API: {"taskId": "ABCD"}


Is there also a way to find this API TaskID and FolderID more easily? Currently, the best process we came up with was to move a folder/task into a folder that we already know the ID of, then do an API call to the folder pull up the IDs, after we get their IDs we move it out of the initial folder.

0
Комментариев: 6
Spot On Innovative Approach Stellar Advice
Avatar

Has anyone come up with this? I am having the same issue.

Why separate the IDs?

0
Действия с комментариями Постоянная ссылка
Spot On Innovative Approach Stellar Advice
Avatar

I can't speak to why the IDs are different, but I constantly need to look up IDs for the API, and I've found the fastest way to do this is using Postman. There's a good pinned article at https://help.wrike.com/hc/en-us/community/posts/115000282125-Beginners-Guide-Get-Data-From-Wrike-s-API-Without-Coding-via-Postman describing how to do this.

My go-to calls are:

I then search the response body within Postman to get the IDs I need based on the folder or task name.

0
Действия с комментариями Постоянная ссылка
Spot On Innovative Approach Stellar Advice
Avatar

Thanks for the response, Laura Boylan, that is currently one of our team's go-to solution other than pulling this id via the Folder/Task Permalink.

One of the most recent issues we are finding with this, however, is trying to grab the ID for something like spaces. During a direct GET call to the api endpoint GET spaces https://developers.wrike.com/documentation/api/methods/get-spaces

Where the spaces return a 500 error and no permalink is visibly found as grabbing a folder id or task id. 

 

0
Действия с комментариями Постоянная ссылка
Spot On Innovative Approach Stellar Advice
Avatar

Russell Wilkie - That's odd. I'm not seeing any problem with the response returned by https://www.wrike.com/api/v4/spaces on our account. Wrike Support may need to assist if you're getting 500 errors here.

0
Действия с комментариями Постоянная ссылка
Spot On Innovative Approach Stellar Advice
Avatar

This is the dumbest way to setup an api 🙄

2
Действия с комментариями Постоянная ссылка
Spot On Innovative Approach Stellar Advice
Avatar

The Wrike v4 API provides a method for converting legacy IDs (i.e., the IDs shown in the url when accessing data via the Wrike front-end): https://developers.wrike.com/api/v4/ids/

For example, a GET call to the following url would retrieve the v4 ID for a task from its legacy ID 1234:

https://www.wrike.com/api/v4/ids?ids=[1234]&type=ApiV2Task

Per the developer documentation this can be performed for the legacy IDs for:

  • Accounts (ApiV2Account)
  • Users and Groups (ApiV2User)
  • Folders (ApiV2Folder)
  • Tasks (ApiV2Task)
  • Comments (ApiV2Comment)
  • Attachments (ApiV2Attachment)
  • Timelog Entries (ApiV2Timelog)

Garrett McCutcheon Community Team at Wrike Узнайте о самых популярных функциях Wrike и советах по его использованию

0
Действия с комментариями Постоянная ссылка

Folllowing List for Post: Wrike Task IDs vs API Ids
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post