Okapi Okapi

Bandwidth API /api/v1/accounts/{id}/billingreports* endpoint removal

Stopped workingSubscribe to Bandwidth APIShare

Calls to /api/v1/accounts/{id}/billingreports* on Bandwidth API stopped working on February 1, 2026.


Calls it hits

  • /api/v1/accounts/{id}/billingreports*

What to use instead of these calls

Download usage, charge, and number reports using the Insights Reports API instead.

In Bandwidth API's words

Effective February 1, 2026, customers will no longer access billing reports under Billing in the Bandwidth App or via the /billingreports endpoints;

Bandwidth API, Announcement

Facts

API
Bandwidth API api.bandwidth.com
Kind
Endpoint removal
Takes effect
February 1, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Bandwidth API's own pages

Questions

When does this change take effect?

Calls to /api/v1/accounts/{id}/billingreports* on Bandwidth API stopped working on February 1, 2026.

What happens to calls after February 1, 2026?

They have failed since February 1, 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 Bandwidth API 1

  1. No date /api/v1/accounts/{id}/bdrs*Endpoint 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.

Add to GitHub

Get notifications

Subscribe to Bandwidth API

Hear about each breaking change Bandwidth API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Bandwidth API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.