ArcGIS Elevation Service
token body parameter removal on POST /arcgis/rest/services/elevation-service/v1/elevation/at-many-points
Deprecated, no dateSubscribe to ArcGIS Elevation ServiceShare
ArcGIS Elevation Service has deprecated the token body parameter on POST /arcgis/rest/services/elevation-service/v1/elevation/at-many-points without a shutdown date. Calls that continue to rely on this parameter will eventually fail once it is removed.
Calls it hits
POST /arcgis/rest/services/elevation-service/v1/elevation/at-many-pointsbody parameter token
What to use instead of these calls
Send the access token in an Authorization: Bearer header instead of using the token property in the request body.
In ArcGIS Elevation Service's words
Deprecated token property in the at-many-points POST body. The preferred approach is to use the authorization header with the Bearer scheme.
Facts
- API
- ArcGIS Elevation Service
elevation-api.arcgis.com - Kind
- Parameter removal
- Announced
- June 18, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against ArcGIS Elevation Service's own pages
Questions
When does this change take effect?
ArcGIS Elevation Service deprecated POST /arcgis/rest/services/elevation-service/v1/elevation/at-many-points, body parameter token without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: ArcGIS Elevation Service 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.