Fastly API
/billing/v2/* version retirement
Stopped workingSubscribe to Fastly APIShare
Calls to /billing/v2/* on Fastly API stopped working on March 4, 2025.
Calls it hits
/billing/v2/*
What to use instead of these calls
Read invoices with the Invoices API (/billing/v3/invoices) instead.
In Fastly API's words
The billing/v2 endpoints are being retired, as the switch to v3 endpoints is now required.
Facts
- API
- Fastly API
api.fastly.com - Kind
- Version retirement
- Takes effect
- March 4, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Fastly API's own pages
Questions
When does this change take effect?
Calls to /billing/v2/* on Fastly API stopped working on March 4, 2025.
What happens to calls after March 4, 2025?
They have failed since March 4, 2025.
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 Fastly API 2
-
/security/*Endpoint removal Stopped working -
No date
POST /userEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.