Polygon Amoy RPC Endpoints & Testnet API

Polygon Amoy RPC Endpoints

Polygon Amoy is the official testnet for Polygon PoS, anchored to Ethereum Sepolia. It provides a low-stakes environment for developers to test smart contracts, dApps, and infrastructure before mainnet deployment. OnFinality offers managed RPC endpoints for Polygon Amoy, giving you reliable access without running your own node.

What is Polygon Amoy?

Launched in January 2024, Amoy replaces the deprecated Mumbai testnet. It mirrors Polygon PoS mainnet (Chain ID 137) with identical EVM behavior, making it ideal for contract testing, QA, staging releases, wallet integration testing, and backend validation. The testnet uses POL as gas token and has a block time of 2-3 seconds.

Why Use OnFinality for Polygon Amoy RPC?

OnFinality provides authenticated RPC endpoints with higher rate limits and clearer usage visibility compared to public endpoints. Key features include:

• Archive and trace support: Access historical state and debug transactions for in-depth testing.
• HTTP and WebSocket transports: Choose the protocol that fits your application.
• Request analytics: Monitor usage, errors, and limits through the OnFinality dashboard.
• Scaling path: Start with shared API endpoints and upgrade to higher-capacity plans as your needs grow.

How to Connect

1. Create or sign in to your OnFinality account.
2. Select Polygon Amoy from the supported networks list.
3. Create an API endpoint (shared or dedicated if available).
4. Test with eth_blockNumber.
5. Monitor usage and move critical traffic to authenticated endpoints.

Polygon Amoy Network Details

| Property | Value | |----------|-------| | Network Name | Amoy | | Chain ID | 80002 | | Gas Token | POL | | Parent Chain | Sepolia | | Block Explorer | https://amoy.polygonscan.com |

Use Cases

• Smart contract testing: Deploy and interact with contracts in a safe environment.
• QA and staging: Validate releases before mainnet deployment.
• Wallet integration: Test wallet connections and transactions.
• Backend validation: Ensure backend services handle blockchain data correctly.

Public vs Authenticated RPC

Public RPC endpoints are suitable for quick experiments but often have rate limits and no observability. OnFinality's authenticated endpoints provide stable access, request analytics, and a clear path to higher capacity for team projects and production-like workloads.

Polygon Amoy RPC resources

Polygon Amoy users are usually preparing Polygon releases, so the page should make testnet RPC access, QA checks, and upgrade paths clear.

Best fit: testnet testing workflows for testing contracts, QA, and release validation.

What builders usually check first:

• Run contract, wallet, and backend checks before sending users to mainnet.
• Keep QA and staging environments close to the production chain model.
• Validate reads, writes, and event handling with low-risk test traffic.
• Move from shared testnet access to mainnet or dedicated infrastructure when release traffic becomes predictable.

Supported capability notes:

• Authenticated Polygon Amoy RPC/API access for testing contracts, QA, and release validation.
• HTTP and WebSocket support for app, backend, and integration workflows.
• Archive access for historical state, analytics, or compliance-style queries.
• Trace support for debugging transactions and deeper execution analysis.
• A safer environment for contract testing, wallet integration, QA, and release checks.

Decision notes:

• Environment: testnet. Protocol family: EVM JSON-RPC.
• HTTP and WebSocket support is listed for supported app and backend workflows.
• Archive support is available for historical state or older chain-data queries.
• Trace support is available for transaction debugging and execution analysis.

A quick connection check usually starts with eth_blockNumber, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.

Planning the next step:

• Use this network for integration confidence first: contract calls, wallet flows, event handling, and backend jobs.
• Before launch, repeat the same checks against the target mainnet and review pricing or dedicated-node needs.

Next steps:

• Create or manage RPC endpoints
• Review RPC pricing
• Read the Polygon Amoy RPC guide