Upcoming webhook improvements [Updated: Launched!]

[Phil_Seeman]

Hi @Seth,

Actually what you’re seeing is completely unrelated to this upcoming change; what you’ve run into is this change to webhook structure:

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

Hi all, we have a new update to share. Our above plan is still accurate, and we’re aiming to let developers start migrating in early November. Notably, though, the plan is missing one crucial component: webhooks. Our deprecations framework is built into our framework for handling API requests. Webhooks, however, originate from within Asana’s API and are not made in response to any request. Client don’t send any headers, and so there’s no way to use those headers to define behavior. Because of t…

That change was announced many months ago and has been slowly rolled out, but yesterday was made live for good; see:

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

Hello all, we have an important update to share about the timeline of this deprecation. Because this deprecation affects literally every API request and webhook, there’s a risk that we will cause a large number of heavily-used apps to encounter errors for extended periods of time if we change the default behavior in an instant on the activation date. In fact, in the last month, nearly 7,000 apps with over 230,000 users have not opted in or out of the deprecation and will almost certainly break …

You’re right, though; looks like the documentation still needs to be updated. (@Joe_Trollo…)