QuickNode RPC URL: How to Find, Use, and Manage Your Endpoint

What a QuickNode RPC URL Is

A QuickNode RPC URL is a unique HTTPS or WSS endpoint that connects your application to a blockchain node operated by QuickNode. Instead of running and maintaining your own node, you send JSON-RPC requests to this URL, and QuickNode routes them to the appropriate network.

The URL is tied to a specific endpoint you create in the QuickNode dashboard. Each endpoint is associated with one blockchain network, such as Ethereum, Solana, Polygon, or Base, and may include add-ons or specific chain configurations.

Because the endpoint is unique to your account, it often contains a token or subdomain that acts as a credential. Treat the full URL as sensitive information, similar to an API key.

• HTTPS endpoints are used for standard request-response JSON-RPC calls.
• WSS endpoints are used for WebSocket subscriptions such as new blocks or logs.
• Each endpoint is scoped to a single blockchain network.
• The URL format typically includes a network name and a unique identifier.

https://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/

How to Find Your QuickNode RPC URL

You can find your QuickNode RPC URL after logging into the QuickNode dashboard and selecting an endpoint. The dashboard displays the HTTP and WSS URLs for that endpoint, along with any API keys or tokens required for add-ons.

If you have not created an endpoint yet, you will need to do so first. The process usually involves choosing a chain, selecting a network, and optionally adding features such as archive data or marketplace add-ons.

The exact dashboard layout and labels may change over time, but the endpoint details page is generally where the RPC URL is shown.

• Log in to the QuickNode dashboard.
• Select or create an endpoint for the network you want to use.
• Open the endpoint details page.
• Copy the HTTP URL for standard RPC calls or the WSS URL for subscriptions.

QuickNode RPC URL Format and Examples

QuickNode RPC URLs generally follow a consistent pattern, though the exact hostname and path depend on the network and endpoint configuration. The URL usually includes a subdomain that identifies the endpoint and a long token that authenticates requests.

For Solana, the endpoint may look similar to other networks but will route JSON-RPC calls to the Solana cluster. For EVM chains, the same URL structure is used to send eth_* methods.

Below are generic examples. Replace the placeholder values with the actual URL from your dashboard.

• HTTPS example: https://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/
• WSS example: wss://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/
• Solana HTTPS example: https://example-solana.quiknode.pro/0000000000000000000000000000000000000000/
• Always use the exact URL provided in the dashboard, including any trailing slash if present.

https://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/

Using the URL with Web3 Libraries

Once you have your QuickNode RPC URL, you can use it with popular Web3 libraries such as ethers.js, web3.js, viem, or Solana Web3.js. The URL is passed as the provider or connection endpoint.

For EVM chains, you typically create a provider or public client with the HTTP URL. For Solana, you create a connection with the URL and optionally a commitment level.

The same URL can often be used in wallets, development frameworks, and backend services that accept a custom RPC endpoint.

• ethers.js: new ethers.JsonRpcProvider('YOUR_QUICKNODE_URL')
• web3.js: new Web3('YOUR_QUICKNODE_URL')
• viem: createPublicClient({ transport: http('YOUR_QUICKNODE_URL') })
• Solana Web3.js: new Connection('YOUR_QUICKNODE_URL', 'confirmed')

const provider = new ethers.JsonRpcProvider('https://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/');

Security and Key Management

Because the QuickNode RPC URL contains an authentication token, it should not be exposed in client-side code, public repositories, or shared logs. If the URL is leaked, others may consume your endpoint's resources.

Use environment variables or a secrets manager to store the URL in server-side applications. For frontend applications, consider using a proxy or a restricted key if QuickNode offers that option for your plan.

If you suspect the URL has been compromised, you can usually rotate or regenerate the endpoint token from the dashboard. Check the current dashboard options for the exact procedure.

• Never commit the full RPC URL to a public GitHub repository.
• Use environment variables such as QUICKNODE_RPC_URL in backend code.
• Avoid logging the full URL in production logs.
• Rotate the endpoint token if it is exposed.

Common Issues and Troubleshooting

If your QuickNode RPC URL is not working, start by verifying that you copied the full URL, including the token and any trailing slash. A missing character can cause authentication or routing errors.

Check that the endpoint is active in the dashboard and that you are using the correct network. Sending Ethereum requests to a Solana endpoint, for example, will not work.

If you are using WSS, ensure your client supports WebSocket connections and that your network allows outbound WSS traffic. Some hosting providers or corporate networks block WebSocket connections.

Rate limits and method restrictions depend on your plan and endpoint configuration. If you receive errors about rate limits or unsupported methods, review your plan details or contact QuickNode support.

• Verify the URL is complete and matches the dashboard exactly.
• Confirm the endpoint is for the correct blockchain network.
• Check that your plan supports the methods you are calling.
• Test the URL with a simple curl request to isolate client issues.

curl -X POST https://example-endpoint.quiknode.pro/0000000000000000000000000000000000000000/ -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

QuickNode RPC URL vs Other Providers

QuickNode is one of several RPC providers. Others include Alchemy, Infura, and public RPC endpoints. The main differences are in supported networks, add-ons, pricing, and performance characteristics.

A QuickNode RPC URL is specific to QuickNode's infrastructure. If you switch providers, you will need to replace the URL in your application with the new provider's endpoint.

When comparing providers, consider factors such as network coverage, archive data availability, WebSocket support, and the specific methods your application needs.

• QuickNode and Alchemy both offer multi-chain RPC services with dashboards and API keys.
• Public RPC endpoints are free but often rate-limited and not suitable for production.
• The best choice depends on your chain, latency requirements, and budget.
• Always test a provider with your actual workload before committing.

Frequently Asked Questions

Below are answers to common questions about QuickNode RPC URLs. For account-specific details, refer to the QuickNode dashboard or support documentation.

• Can I use the same QuickNode RPC URL for multiple chains? No, each endpoint is tied to one network.
• Is the QuickNode RPC URL free? QuickNode may offer a free tier, but limits and features vary by plan.
• How do I find my QuickNode RPC URL? Log in to the dashboard and open your endpoint details.
• Can I share my QuickNode RPC URL? It is not recommended because it contains an authentication token.
• What is the difference between HTTP and WSS URLs? HTTP is for request-response calls; WSS is for subscriptions.