Hi everyone! Unfortunately this is one of my announcements that doesn’t include a new feature launch, sorry. :slightly_frowning_face: However, this one is much more important to read, as it is guaranteed to cause your code to break. Asana currently uses numerical IDs for all references, but we are…

We resolved the issue and as of noon PST yesterday, the Asana API no longer supports numeric IDs. It’s been two years since we started planning this deprecation and 18 months since we first published communications about it. Thank you all so much for your patience and understanding throughout this t…

Said a guy who’s going to get to do a lot of manual labor since php-asana no longer seems to function, and sorting out how to make it work again is a task I’m giving up on.

@ctam —Sorry for the trouble there. I’m not sure what’s wrong but I’ll pass this along to the engineer responsible for the Ruby client library who will investigate. @Adam_Lambert —I’m sorry that this deprecation caught you off-guard. We tried our best to communicate these changes through a number of …

I finally got it working by adding a hack to send the Asana-Disable: string_ids header. I am still having no idea what needs to be done to make the php-asana (the official one) client use the string based id’s. I hope/assume whoever works on the php-asana library is aware that it’s broken and wi…

And to be clear, my beef was less that a change had to be made, and more that it got made right before a long weekend.

Hello all, I have a rather unfortunate update. Sometime between when we did all the engineering and testing work for string IDs about 10 months ago and when we activated the string ID change this past month, we introduced a bug in our configuration. This impact of this bug is that only some routes …

Hello all, Upon assessing the fallout from the most recent “bump” (which properly affected the entire API) we have decided that changing the default behavior across the entire API tomorrow as scheduled would negatively affect far more of our users than we’re comfortable with. As such we are cancell…

Thanks for the update, good luck :wink:

Right? I just read and felt like… ohh man you don’t have anything better to do than making us redo all our stuff?

[image] Cezar_Ayran: making us redo all our stuff This is actually a pretty minor change in the code, replacing id with gid and update typings :slight_smile: Did you manage to do it?

Asana is moving to string IDs [Updated with revised timeline]

English Forum Developers & API

Bastien_Siebman 14 September 2019 05:52 40

Thanks a lot for the detailed answer, really interesting! Good luck on the fix.

Topic		Replies	Views
Get a custom field used to return "id" but it isn't anymore? Developers & API tasks	8	2158	21 February 2020
Venting about the API system! Developers & API	3	2158	30 October 2019
API Error: GID deprecation seems broken Developers & API	1	1841	28 August 2019
Reminder about two big upcoming API changes (String IDs and new sections) Platform News	14	11360	10 July 2019
Asana events giving resource id as null Developers & API	4	2641	4 September 2019

Asana is moving to string IDs [Updated with revised timeline]

Related topics