nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Converting Current API IDs to Legacy V2

Perry Grimwood

Hello,

I know that there is an API call to convert legacy IDs to the current IDs, but is the inverse possible? I am working on a project that is importing task information into a database, and it would be ideal if the ID stored in the database matched the legacy v2 numeric ID seen on the front end instead of the current alphanumeric ID v4 uses.

For example, let's say I am importing Project #1, which shows an ID of 4527100000 on the Wrike website, but the API ID is MAAAAAabcd. I would like the database to store the ID as 4527100000.

Alternatively, is there a way to get the current API IDs to show on the front end instead of the legacy IDs?

Find more posts tagged with

tasks

api

Accepted answers

Rohan V

Welcome to the Community, @Perry Grimwood! 👋

Thank you for posting your question here. I’m looping in our Support team to assist you further with this query. One of our experts will be in touch with you shortly 👍

All comments

Rohan V

Bill Fry

I'm having the same issue when trying to work with Wrike Analyze, which wants the numeric ID for custom fields and not the current ones used by the API. I tried pulling the details from the API to see if it would provide the older numeric ID, but it doesn't.

Perry Grimwood

The Support Team told me I can pull the legacy IDs from the Permalink field found in Get Task calls, since the URL used in Wrike uses the legacy ID. I extracted that field and created a substring that only uses characters after the = sign in the permalink. I accomplished my goal via this method.