Skip to content
Alchemy Logo

Injective API FAQ

Frequently asked questions about the Injective API

Injective is a high-performance Layer 1 blockchain built on the Cosmos SDK, purpose-built for decentralized finance (DeFi) applications such as decentralized exchanges, prediction markets, and lending protocols. It features full EVM compatibility, allowing developers to deploy Ethereum-based smart contracts while benefiting from fast finality and low transaction costs.

See the Injective API quickstart guide to start building on Injective.

The Injective API lets you interact with Injective Mainnet and Injective Testnet. You can execute transactions, query onchain data, and interact with the network using the JSON-RPC standard.

Yes, Injective is EVM compatible.

Injective uses the JSON-RPC API standard. This API enables blockchain interaction on the Injective network, letting you read block and transaction data, query chain information, execute smart contracts, and store data onchain.

Injective supports the standard Ethereum JSON-RPC surface for both mainnet and testnet. A few methods (eth_getBlockReceipts, eth_syncing, and net_listening) are enabled on Injective Testnet only; each of those method reference pages calls that out in its description. For debug_* methods, use the separate Debug API documentation (its OpenRPC spec is not the Injective chain spec). See the Injective API overview for chain IDs and the full Node API method list.

When you access the Injective network through a node provider like Alchemy, you use an API key to send transactions and retrieve data. We recommend you sign up for a free API key.

Common Ethereum libraries like ethers.js are compatible with Injective, given its EVM nature.

If you have questions or feedback, contact us at [email protected] or open a ticket in the Alchemy Dashboard.

Was this page helpful?