Helius RPC URL: How to Find and Use Your Solana Endpoint

What a Helius RPC URL Is

A Helius RPC URL is the web address your application uses to send Solana JSON-RPC requests to Helius. Instead of running your own Solana node, you point your client at this URL and Helius routes the request to its infrastructure. The URL is the connection string for standard Solana RPC methods such as getBalance, getLatestBlockhash, sendTransaction, and getAccountInfo.

The URL is tied to your Helius account through an API key. That key appears as a query parameter in the endpoint, which is why the full URL should be treated as sensitive. The exact hostname and path can change as Helius updates its infrastructure, so always confirm the current format in your Helius dashboard or official documentation.

• Purpose: connect Solana clients to Helius RPC nodes.
• Typical form: https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY
• Contains: a network host and your personal API key.
• Used by: web3.js, Anchor, solana-cli, curl, and other Solana tooling.

https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY

How to Find Your Helius RPC URL

The most reliable place to find your Helius RPC URL is the Helius dashboard. After you sign up and create a project, the dashboard displays the endpoint associated with that project. The URL is generated for you; you do not need to construct it manually.

If you are working in a team, make sure you are using the endpoint for the correct project. Helius accounts can contain multiple projects, and each project can have its own API key and endpoint. Copying the wrong URL is a common source of confusion when transactions appear to go to the wrong environment.

• Sign in to the Helius dashboard.
• Open or create a project.
• Locate the RPC endpoint or API key section.
• Copy the full HTTPS URL, including the api-key query parameter.
• Store it in an environment variable rather than hard-coding it.

Helius RPC URL Structure

A Helius RPC URL generally combines a base host, a network path, and an API key query parameter. The base host identifies Helius, while the API key tells Helius which account and project the request belongs to. Some endpoints may also include a network segment such as mainnet or devnet.

Because Helius can update hostnames and supported networks, treat any example as a template rather than a permanent constant. The authoritative value is always the one shown in your dashboard. If you are migrating from another provider, you can usually replace the old RPC URL with the Helius URL without changing your application code.

• Base host: the Helius RPC domain.
• Network path: indicates mainnet, devnet, or another supported network.
• API key: passed as a query parameter, for example ?api-key=YOUR_API_KEY.
• Full URL: base host + network path + API key.

https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY

Using the Helius RPC URL with Solana Tools

Once you have your Helius RPC URL, you can use it anywhere a Solana RPC endpoint is accepted. In JavaScript and TypeScript, the @solana/web3.js Connection object takes the URL as its first argument. In Rust, you can pass the same URL to a Solana RPC client. The solana-cli also accepts a custom URL through its configuration.

For quick tests, curl is often the fastest way to confirm that your URL and API key work. A successful response returns JSON with a result or an error field. If you see an authentication error, the API key is likely missing, incorrect, or associated with a different project.

• web3.js: new Connection('https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY')
• Anchor: set the provider connection to your Helius URL.
• solana-cli: use the --url flag or update your CLI config.
• curl: send a JSON-RPC POST request to the URL.

const { Connection } = require('@solana/web3.js');
const connection = new Connection('https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY');

const version = await connection.getVersion();
console.log(version);

Testing Your Helius RPC URL with curl

A curl request is a simple way to verify that your Helius RPC URL is reachable and that your API key is accepted. The request sends a JSON-RPC method such as getVersion or getHealth. If the endpoint is working, you receive a JSON response with a result. If not, the response usually contains an error message that points to the problem.

Keep in mind that public examples may use placeholder keys. Replace YOUR_API_KEY with the value from your Helius dashboard. Avoid sharing the full URL in screenshots, public repositories, or support tickets, because anyone who has it can consume your account's request capacity.

• Use POST requests with Content-Type: application/json.
• Start with a lightweight method like getVersion or getHealth.
• Check for a result field in the response.
• Never commit a real API key to version control.

curl https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getVersion"}'

Helius RPC URL vs Helius gRPC

The Helius RPC URL is an HTTP JSON-RPC endpoint. It is the standard way to read Solana account data, submit transactions, and query block information. Helius also offers gRPC, which uses a different protocol and is often used for streaming account updates, slots, and transactions with lower overhead.

If your application needs request-response access to Solana RPC methods, the HTTPS RPC URL is usually the right choice. If you need high-throughput streaming or real-time data, gRPC may be a better fit. The two are not interchangeable; they serve different client patterns. Check the Helius documentation for the current gRPC endpoint format and supported features.

• RPC URL: HTTP JSON-RPC, request-response, broad method support.
• gRPC: streaming-oriented, often used for real-time data.
• Use RPC for standard Solana client operations.
• Use gRPC when you need continuous streams or lower-latency updates.

Keeping Your Helius RPC URL and API Key Secure

Your Helius RPC URL contains an API key, so it should be handled like a credential. Store it in environment variables, a secrets manager, or a server-side configuration file that is not committed to source control. For browser or mobile applications, avoid exposing a privileged key directly; use a backend proxy or a restricted key where available.

If a key is leaked, rotate it in the Helius dashboard as soon as possible. Rotation invalidates the old URL and generates a new one, so you will need to update your application configuration. Review your usage regularly to catch unexpected traffic, and use separate projects or keys for development and production when possible.

• Use environment variables such as HELIUS_RPC_URL.
• Do not hard-code keys in client-side code.
• Rotate keys if they are exposed.
• Separate development and production projects.
• Monitor usage in the Helius dashboard.

HELIUS_RPC_URL=https://mainnet.helius-rpc.com/?api-key=YOUR_API_KEY

Common Questions About the Helius RPC URL

People often search for Helius RPC URL examples, reviews, tutorials, pricing, and API key help. The URL itself is straightforward: it is the endpoint you copy from the dashboard and paste into your Solana client. Reviews and pricing change over time, so check the official Helius website and dashboard for current plan details rather than relying on third-party summaries.

If you are following a Helius RPC tutorial, the main steps are consistent: create an account, create a project, copy the RPC URL, and use it in your code. If you see a Helius RPC Reddit thread or review, treat it as anecdotal and verify technical details against the official documentation. For API key issues, confirm that the key is present in the URL and that the project is active.

• Helius RPC URL: the endpoint for Solana JSON-RPC requests.
• Helius Solana RPC: the service that powers the endpoint.
• Helius RPC API key: the credential embedded in the URL.
• Helius RPC pricing: check the official site for current plans.
• Helius gRPC: a separate streaming endpoint, not the same as the RPC URL.