Treasury Prime API
GET /search endpoint removal
Stopped workingSubscribe to Treasury Prime APIShare
Calls to GET /search on Treasury Prime API stopped working on March 20, 2026.
Calls it hits
GET /search
What to use instead of these calls
Migrate calls to the relevant resource-specific endpoints, such as GET /account or GET /person, before the removal date.
In Treasury Prime API's words
The /search endpoint is being deprecated and will be permanently removed on March 20, 2026.
Facts
- API
- Treasury Prime API
api.treasuryprime.com - Kind
- Endpoint removal
- Takes effect
- March 20, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Treasury Prime API's own pages
Questions
When does this change take effect?
Calls to GET /search on Treasury Prime API stopped working on March 20, 2026.
What happens to calls after March 20, 2026?
They have failed since March 20, 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 Treasury Prime API 1
-
GET /transactionEndpoint removal Stops workingin 59 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.