QuickNode API
Functions REST API removal
Deprecated, no dateSubscribe to QuickNode APIShare
QuickNode has deprecated the Functions REST API without setting a shutdown date. QuickNode API announced that the feature will no longer be available soon. All calls to /functions/* endpoints will fail once the removal takes effect.
Calls it hits
/functions/*
What to use instead of these calls
Run the function's logic in your own serverless runtime fed by QuickNode Streams or Webhooks. Moving away from Functions takes more than changing an identifier, as QuickNode names no direct replacement and teams must decide where their code runs next.
QuickNode names no replacement for Functions: where the code runs next is the team's call.
In QuickNode API's words
Quicknode Functions will be deprecated and will no longer be available soon.
Facts
- API
- QuickNode API
api.quicknode.com - Kind
- Removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against QuickNode API's own pages
Questions
When does this change take effect?
QuickNode API deprecated /functions/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: QuickNode 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 QuickNode API 2
-
/graphqlRemoval Stopped working -
/quickalerts/*Removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.