Infura RPC URL: How to Find, Format, and Use Your Endpoint

What an Infura RPC URL Is

An Infura RPC URL is the endpoint address your application sends JSON-RPC requests to when it wants to read or write data on a supported blockchain network. Instead of running your own node, you point your wallet, script, or dApp at an Infura URL and Infura handles the node infrastructure behind it.

The URL is tied to a project inside your Infura account and includes a project ID, which acts as the credential for that endpoint. Because the project ID is embedded in the URL, the endpoint should be treated as sensitive and kept out of public repositories and client-side code where possible.

Infura supports multiple networks, and each network has its own endpoint path. Ethereum mainnet, testnets, and other supported chains each get a distinct URL under the same project.

• The URL routes JSON-RPC calls to Infura-managed nodes.
• It contains a project ID that identifies your account project.
• Different networks use different endpoint paths.
• Both HTTPS and WebSocket variants are typically available.

Infura RPC URL Format

Infura endpoints follow a consistent structure. The most common form is an HTTPS URL that includes the network name and your project ID. WebSocket endpoints use the wss scheme and a similar path.

The exact host and path can change as Infura updates its infrastructure, so always confirm the current format in your Infura dashboard rather than copying an old example. The patterns below show the general shape of the URL.

• HTTPS mainnet pattern: https://mainnet.infura.io/v3/YOUR_PROJECT_ID
• WebSocket mainnet pattern: wss://mainnet.infura.io/ws/v3/YOUR_PROJECT_ID
• Sepolia testnet pattern: https://sepolia.infura.io/v3/YOUR_PROJECT_ID
• Replace YOUR_PROJECT_ID with the ID from your Infura project.

https://mainnet.infura.io/v3/YOUR_PROJECT_ID
wss://mainnet.infura.io/ws/v3/YOUR_PROJECT_ID
https://sepolia.infura.io/v3/YOUR_PROJECT_ID

How to Find Your Infura RPC URL

Your Infura RPC URL is generated when you create a project in the Infura dashboard. After signing in, open the project you want to use and look for the endpoint list. Each supported network shows its own URL, and you can copy the one that matches the chain you are targeting.

If you are looking for an Infura RPC login, note that Infura uses an account sign-in rather than a separate RPC login. You sign in to the dashboard, select a project, and copy the endpoint from there. The project ID in the URL is what authenticates your requests.

Keep a record of which project ID belongs to which application. If you rotate or delete a project, any URL that uses its ID will stop working.

• Sign in to the Infura dashboard and open your project.
• Find the endpoint list for the network you need.
• Copy the HTTPS or WebSocket URL shown for that network.
• Store the project ID securely and avoid exposing it publicly.

Using the URL with Wallets and Libraries

Most Ethereum tools accept an Infura RPC URL as a custom network endpoint. In a browser wallet, you can add a network manually and paste the HTTPS URL into the RPC field. The wallet then sends its requests through Infura.

In code, popular libraries such as ethers.js and web3.js accept the URL as a provider argument. The example below shows the general pattern; the exact constructor may differ by library version.

• Browser wallets: add a custom network and paste the HTTPS URL.
• ethers.js: pass the URL to a JsonRpcProvider.
• web3.js: pass the URL to a Web3 HTTP provider.
• WebSocket URLs are used for subscriptions and real-time events.

const provider = new ethers.JsonRpcProvider("https://mainnet.infura.io/v3/YOUR_PROJECT_ID");
const blockNumber = await provider.getBlockNumber();
console.log(blockNumber);

Infura API Key and Project ID

The project ID in an Infura RPC URL is sometimes called an API key. It identifies your project and is used to attribute requests to your account. Infura may also support separate API keys for specific products, so check the dashboard for the credential that applies to the endpoint you are using.

Because the project ID is part of the URL, anyone who obtains it can send requests against your project. Use environment variables, server-side proxies, or restricted keys where available to reduce exposure.

If you need to rotate a credential, generate a new project or key in the dashboard and update your applications to use the new URL.

• The project ID is embedded in the RPC URL.
• Treat the URL as a secret credential.
• Use environment variables instead of hardcoding it.
• Rotate the project ID if it is exposed.

Infura RPC Pricing and Limits

Infura offers a free tier and paid plans, and the request limits, features, and pricing can change over time. Rather than relying on a fixed number, check the current Infura pricing page for the latest details on daily requests, archive data access, and add-on services.

If you search for Infura RPC pricing, compare the plan limits against your expected request volume. High-traffic applications may need a paid plan or a dedicated endpoint to avoid rate limiting.

For teams that need multi-chain coverage or a different pricing model, other providers exist, but the right choice depends on your specific networks and workload.

• Free and paid tiers are available; limits vary by plan.
• Check the official pricing page for current quotas.
• Rate limits apply per project and can affect high-traffic apps.
• Archive data and add-on services may require a paid plan.

Infura RPC GitHub and Developer Resources

Infura maintains developer documentation and open-source examples. Searching for Infura RPC GitHub will surface client libraries, sample projects, and community tools that show how to connect to an Infura endpoint.

The official documentation is the most reliable source for current endpoint formats, supported networks, and API methods. Use it alongside any GitHub examples, since community code may target older URL patterns.

• Official docs cover endpoint formats and supported networks.
• GitHub examples can help with library integration.
• Verify examples against current documentation.
• Community tools may use outdated URL structures.

Troubleshooting a Failing Infura RPC URL

If your Infura RPC URL stops working, the cause is often a missing or incorrect project ID, a network mismatch, or a rate limit. Start by confirming that the URL matches the network you intend to use and that the project ID is current.

Check the response body for an error code or message. Authentication errors usually point to an invalid project ID, while rate-limit errors indicate too many requests. Network errors may mean the endpoint path is wrong or the service is temporarily unavailable.

If you recently changed projects or rotated credentials, update every place the old URL appears, including environment files, CI secrets, and deployed services.

• Verify the project ID is correct and active.
• Confirm the URL path matches the target network.
• Check for rate-limit or authentication error messages.
• Update all references after rotating credentials.

Infura IPFS and Other Services

Infura also offers IPFS and other Web3 infrastructure services alongside its RPC endpoints. These use different URLs and credentials from the blockchain RPC URL, so do not mix them up when configuring your application.

If you are looking for Infura IPFS, check the dedicated documentation for its endpoint and authentication method. The RPC URL guide here applies specifically to JSON-RPC blockchain access.

• IPFS endpoints are separate from RPC endpoints.
• Each service may use its own credentials.
• Check service-specific docs for correct configuration.
• Do not reuse an RPC URL for IPFS requests.