GET /v0/addresses/{}/transactions → endpoint removal
Helius API
Deprecated, no date
The provider has deprecated the GET /v0/addresses/{}/transactions endpoint without a shutdown date. Although existing endpoints continue to operate, the API is no longer receiving new parser types or feature work, and calls will eventually fail.
Calls it hits
GET /v0/addresses/{}/transactions
What to use instead of these calls
Read an address's history using the getTransactionsForAddress RPC method on mainnet.helius-rpc.com.
In Helius API's words
The Enhanced Transactions API is deprecated and no longer receiving new parser types or feature work. Existing endpoints continue to operate
Facts
- API
- Helius API
api.helius.xyz - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Helius API's own pages
Questions
When does this change take effect?
Helius API deprecated GET /v0/addresses/{}/transactions without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Helius 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 Helius API 1
-
No date
POST /v0/transactionsEndpoint 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.