Ashby API
POST /application.change_stage endpoint removal
Deprecated, no dateSubscribe to Ashby APIShare
Ashby API has deprecated the POST /application.change_stage endpoint without setting a shutdown date. Calls made to this route are slated for removal and will fail once it is taken offline.
Calls it hits
POST /application.change_stage
What to use instead of these calls
Call POST /application.changeStage instead.
In Ashby API's words
Deprecated. Use application.changeStage instead.
Facts
- API
- Ashby API
api.ashbyhq.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Ashby API's own pages
Questions
When does this change take effect?
Ashby API deprecated POST /application.change_stage without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Ashby 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 Ashby API 1
-
No date
POST /application.change_sourceEndpoint 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.