Changes in API IDs internal structure

According to this article the API IDs will change after July 1.

It explains what kind of matches NOT to do, as they may not be valid anymore, but doesn't explain what will the new IDs look like and how to do matches correctly.

Am I missing something? In order to prepare our integrations, we should know what the new format will be.

Find more posts tagged with

Comments

Basudha Sakshyarika

Welcome to the Wrike Community, @Dāvis Fridenvalds. I am looping in our support team experts to take a look at your query. Please expect them to reach out soon. Thank you! 😊

Tiffany Sands

@Basudha SakshyarikaIs there an update on this?

Jonathan Burke

Just to add further weight to this - I urgently need further information on this topic too.

The current documentation is completely lacking here.

Rohan V

@Jonathan Burke, thanks for providing your feedback! I can see that you are in touch with our Support Team. I hope they were able to assist you and answer your question. @Tiffany Sands, I have raised a support ticket on your behalf, and one of our API experts will get in touch with you shortly 👍

Alex Chan

I think it mentioned quite clearly that only exact match can be done and should not do any processing of the id such as normalizing it. It doesn't really matter how it looks like as long as it falls within 256 characters and only contains those characters.
The only thing I don't like is include the special character like equal sign, it may cause confusion on parsing url for troubleshooting.

Jonathan Burke

Indeed, after accepting feedback a month and a half ago, last week Wrike added the "Limits" section - finally adding details as to what constitutes a valid match...

^[a-zA-Z0-9\-_:.=]{1,256}$

(Before that there was no such detail, hence the problem.)

Dāvis Fridenvalds

Thanks @Jonathan Burke for pointing that out!
Indeed, the Limits section was not there when I made this thread initially.

Jennifer Wood

Is there a reason all these IDs have changed? For those who use the API with PowerBI, the new format causes all kinds of problems since PowerBI is not case sensitive but all the new IDs now have both cases and special characters. Anybody have any suggestions for how to overcome the new ID format if you're using PowerBI?

Rohan V

Hi @Jennifer Wood 👋 thanks for posting your feedback here.

While we wait to hear suggestions from our Community members, I can ask one of our API experts to assist you. Just let me know, and I’ll go ahead and raise a support ticket on your behalf.