QuickNode Raises $60M Series B!
Read the Letter from our CEO.
Get started with Stacks development using these docs - send suggestions for improvements to email@example.com.
With QuickNode, you get access to our global network which always routes your API requests to the nearest available location, ensuring low latency and fastest speeds.
Token Authentication - By default, all endpoints created on QuickNode are protected by a token in the URL which looks something like this:
Please note the
/ at the end of the URL. Without it, you will receive
Approved Referrer List - For endpoints on the shared network, you are able to add a list of approved referrers. This requires any HTTP request to send a
Referrer header or any WebSocket request to send a
Origin header populated with one of the referrers you entered into our user panel.
Disabling Token Authentication - You can also disable the token authentication completely in your security settings for a given endpoint. This will allow anyone to make requests to the endpoint without the token.
If you're running a dedicated endpoint, you cannot disable token authentication or roll your token - so be careful where you share your endpoint URL!
JWT (JSON Web Tokens) - For additional security, you can also enable JWT for each of your deployed endpoints. JWT allows for stateless authentication between you and your endpoint. Learn how to use JWT with QuickNode in this step-by-step guide.
Multiple Authentication Tokens - Create multiple authentication tokens for each of your deployed endpoints. This allows you to revoke any tokens that may be comprised, without needing to restart your non-compromised endpoint.
To roll an individual authentication token, create an additional token and then delete the previous token. Learn more about multiple authentication tokens in this QuickNode guide.
Most *nix based systems have cURL support out of the box. cURL is a command line tool and library for transferring data with URLs. Check if you have it by running the following:
If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!