Brex API
GET /v1/expenses/card/{id} endpoint removal
Deprecated, no dateSubscribe to Brex APIShare
On May 1, 2025, Brex API announced the deprecation of the GET /v1/expenses/card/{id} endpoint without a shutdown date. Brex API is deprecating Card Expenses endpoints in favor of consolidated Expenses API endpoints. Once retired, calls to this endpoint fail.
Calls it hits
GET /v1/expenses/card/{id}
What to use instead of these calls
Get an expense with GET /v1/expenses/{id} instead.
In Brex API's words
Expenses API: Deprecated Card Expenses API endpoints in favor of consolidated Expenses API endpoints.
Facts
- API
- Brex API
api.brex.com - Kind
- Endpoint removal
- Announced
- May 1, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Brex API's own pages
Questions
When does this change take effect?
Brex API deprecated GET /v1/expenses/card/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Brex API has not given a shutdown date yet.
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 -
POST /v2/users/{id}/limitEndpoint removal Stopped working -
No date
GET /v1/expenses/cardEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.