QuickNode API
QuickAlerts REST API removal
Stopped workingSubscribe to QuickNode APIShare
Calls to /quickalerts/* on QuickNode API stopped working on July 31, 2025.
Calls it hits
/quickalerts/*
What to use instead of these calls
Use QuickNode Webhooks (/webhooks/rest/v1/*) or Streams (/streams/rest/v1/*) for on-chain notifications instead. Moving alerts requires a decision, as Webhooks and Streams are separate products with their own filters and pricing.
Webhooks and Streams are other products with their own filters and pricing: moving the alerts there is the team's call.
In QuickNode API's words
QuickAlerts - QuickAlerts is sunsetting on July 31, 2025.
Facts
- API
- QuickNode API
api.quicknode.com - Kind
- Removal
- Takes effect
- July 31, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against QuickNode API's own pages
Questions
When does this change take effect?
Calls to /quickalerts/* on QuickNode API stopped working on July 31, 2025.
What happens to calls after July 31, 2025?
They have failed since July 31, 2025.
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 QuickNode API 2
-
/graphqlRemoval Stopped working -
No date
/functions/*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.