Asana API
GET /api/1.0/projects/{id}/project_statuses endpoint removal
Deprecated, no dateSubscribe to Asana APIShare
The endpoint GET /api/1.0/projects/{id}/project_statuses has been deprecated without a shutdown date. Calls made to this route are marked for removal and will eventually fail. Asana API notes that integrations should prefer the status_updates route instead.
Calls it hits
GET /api/1.0/projects/{id}/project_statuses
What to use instead of these calls
Call GET /api/1.0/status_updates?parent={project_gid} instead.
In Asana API's words
Deprecated: new integrations should prefer the `/status_updates` route.
Facts
- API
- Asana API
app.asana.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Asana API's own pages
Questions
When does this change take effect?
Asana API deprecated GET /api/1.0/projects/{id}/project_statuses without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Asana API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Asana API 3
-
No date
DELETE /api/1.0/project_statuses/{id}Endpoint removal Deprecated, no date -
No date
GET /api/1.0/project_statuses/{id}Endpoint removal Deprecated, no date -
No date
POST /api/1.0/projects/{id}/project_statusesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.