Webexapis
/v1/people/{id}/features/executiveAssistant endpoint removal
Stopped workingSubscribe to WebexapisShare
On June 15, 2026, the endpoint /v1/people/{id}/features/executiveAssistant stopped working. Calls to this path fail since that date. Webexapis noted that paths for executive assistant settings would change.
Calls it hits
/v1/people/{id}/features/executiveAssistant
What to use instead of these calls
Call /v1/telephony/config/people/{personId}/executive instead.
In Webexapis's words
the API paths for Update and Retrieve Executive Assistant Settings APIs will change
Facts
- API
- Webexapis
webexapis.com - Kind
- Endpoint removal
- Announced
- December 12, 2025
- Takes effect
- June 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Webexapis's own pages
Questions
When does this change take effect?
Calls to /v1/people/{id}/features/executiveAssistant on Webexapis stopped working on June 15, 2026.
What happens to calls after June 15, 2026?
They have failed since June 15, 2026.
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 Webexapis 5
-
POST /docs/api/v1/device-call-settings/modify-device-layout-by-device-idBehaviour change Stopped working -
GET /docs/api/v1/user-call-settings-2-2/get-shared-line-appearance-membersEndpoint removal Stopped working -
PUT /docs/api/v1/user-call-settings-2-2/put-shared-line-appearance-membersEndpoint removal Stopped working -
GET /v1/people/{id}/features/executiveAssistantVersion retirement Stopped working -
PUT /v1/people/{id}/features/executiveAssistantVersion retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.