Aiven API
/v1/billing-group/{id}/invoice endpoint removal
Stopped workingSubscribe to Aiven APIShare
On September 22, 2026, the endpoint /v1/billing-group/{id}/invoice was removed. Calls to this endpoint fail since that date.
Calls it hits
/v1/billing-group/{id}/invoice
What to use instead of these calls
Call /v1/organization/{organization_id}/invoices instead using the organization-level API.
In Aiven API's words
The API endpoint /v1/billing-group/{billing_group_id}/invoice is deprecated. Use https://api.aiven.io/v1/organization/{organization_id}/invoices instead. It will be removed on 2026-09-22.
Facts
- API
- Aiven API
api.aiven.io - Kind
- Endpoint removal
- Takes effect
- September 22, 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/billing-group/{id}/invoice on Aiven API stopped working on September 22, 2026.
What happens to calls after September 22, 2026?
They have failed since September 22, 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/account/{id}/billing-groupEndpoint removal Stopped working -
/v1/billing-groupEndpoint removal Stopped working -
/v1/billing-group/{id}Endpoint removal Stopped working -
/v1/billing-group/{id}/invoice/{id}/csvEndpoint removal Stopped working -
/v1/billing-group/{id}/invoice/{id}/linesEndpoint removal Stopped working -
/v1/billing-group/{id}/projectsEndpoint removal Stopped working -
/v1/invoices/{id}Endpoint removal Stopped working -
DELETE /v1/card/{id}Endpoint removal Stopped working -
GET /v1/cardEndpoint removal Stopped working -
/v1/account/{id}/users/searchEndpoint 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.