Brex API
POST /v2/users/{id}/limit endpoint removal
Stopped workingSubscribe to Brex APIShare
On September 1, 2026, the POST /v2/users/{id}/limit endpoint was removed and is no longer supported. Any requests sent to this endpoint after this date fail. Calls to set user limits using this route are no longer accepted.
Calls it hits
POST /v2/users/{id}/limit
What to use instead of these calls
Set user spend through the Budgets API spend limits by calling POST /v2/spend_limits or PUT /v2/spend_limits/{id}.
In Brex API's words
Team API: Removed the deprecated POST /v2/users/{id}/limit endpoint ( setUserLimit ); it is no longer supported.
Facts
- API
- Brex API
api.brex.com - Kind
- Endpoint removal
- Announced
- September 1, 2026
- Takes effect
- September 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Brex API's own pages
Questions
When does this change take effect?
Calls to POST /v2/users/{id}/limit on Brex API stopped working on September 1, 2026.
What happens to calls after September 1, 2026?
They have failed since September 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 Brex API 3
-
GET /v2/users/{id}/limitEndpoint removal Stopped working -
No date
GET /v1/expenses/cardEndpoint removal Deprecated, no date -
No date
GET /v1/expenses/card/{id}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.