Aiven API
/v1/me/account/invites/reject endpoint removal
Stopped workingSubscribe to Aiven APIShare
Calls to /v1/me/account/invites/reject on Aiven API stopped working on April 21, 2026.
Calls it hits
/v1/me/account/invites/reject
What to use instead of these calls
The endpoint goes without a replacement named: the feature it served has to be redone another way or dropped.
In Aiven API's words
The API endpoint /v1/me/account/invites/reject is deprecated and will be removed on 2026-04-21.
Facts
- API
- Aiven API
api.aiven.io - Kind
- Endpoint removal
- Takes effect
- April 21, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Aiven API's own pages
Questions
When does this change take effect?
Calls to /v1/me/account/invites/reject on Aiven API stopped working on April 21, 2026.
What happens to calls after April 21, 2026?
They have failed since April 21, 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 Aiven API 10
-
/v1/project/{id}/service/{id}/query/statsEndpoint removal Stopped working -
/v1/account/{id}/invite/{id}Endpoint removal Stopped working -
POST /v1/account/{id}/team/{id}/membersEndpoint removal Stopped working -
POST /v1/account/{id}/team/{id}/project/{id}Endpoint removal Stopped working -
DELETE /v1/project/{id}/invite/{id}Endpoint removal Stopped working -
/v1/organization/{id}/vpc/{id}/peering-connection/{id}/user-peer-network-cidrsEndpoint removal Stopped working -
/v1/me/account/invitesEndpoint removal Stopped working -
/v1/me/account/invites/acceptEndpoint removal Stopped working -
/v1/account/{id}/team/{id}/invitesEndpoint removal Stopped working -
/v1/account/{id}/team/{id}/invites/{id}Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.