Linode API (Akamai Cloud)
/{id}/account/child-accounts* endpoint removal
Deprecated, no dateSubscribe to Linode API (Akamai Cloud)Share
Linode API (Akamai Cloud) deprecated the /{id}/account/child-accounts* endpoints without a shutdown date. Calls made to these endpoints will fail. Linode API (Akamai Cloud) notes that this operation is now deprecated.
Calls it hits
/{id}/account/child-accounts*
What to use instead of these calls
Use the Identity and Access delegation operations under /v4/iam/delegation (child-accounts, profile/child-accounts/{euuid}/token) instead.
In Linode API (Akamai Cloud)'s words
This operation is now deprecated, so use the [List child accounts](https://techdocs.akamai.com/linode-api/reference/get-iam-delegation-all-child-accounts) operation instead.
Facts
- API
- Linode API (Akamai Cloud)
api.linode.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Linode API (Akamai Cloud)'s own pages
Questions
When does this change take effect?
Linode API (Akamai Cloud) deprecated /{id}/account/child-accounts* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Linode API (Akamai Cloud) 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 Linode API (Akamai Cloud) 3
-
GET /{id}/lke/clusters/{id}/dashboardEndpoint removal Stopped working -
No date
/{id}/account/entity-transfers*Endpoint removal Deprecated, no date -
No date
/{id}/account/users/{id}/grantsEndpoint 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.