GET /v1/hierarchy → endpoint removal
Checkr API
Deprecated, no date
Checkr has deprecated the GET /v1/hierarchy endpoint without a shutdown date. The provider notes that this endpoint will no longer be supported. Calls to this endpoint will eventually fail.
Calls it hits
GET /v1/hierarchy
What to use instead of these calls
List the account's hierarchy nodes with GET /v1/nodes instead.
In Checkr API's words
Note: This endpoint is deprecated and will no longer be supported. Please use the new List existing Nodes endpoint instead.
Facts
- API
- Checkr API
api.checkr.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Checkr API's own pages
Questions
When does this change take effect?
Checkr API deprecated GET /v1/hierarchy without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Checkr 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.