Injective · Authentication Profile
Injective Authentication
Authentication
Injective's public read APIs (Chain LCD/REST, Tendermint RPC, and the Indexer gRPC/gRPC-web/REST + Chain Stream WebSocket) are open, permissionless endpoints that require no API key or OAuth token — they are rate-limited public infrastructure. WRITE access is not key-based: state changes are performed by broadcasting cryptographically signed transactions. Signing uses either native Cosmos secp256k1 (bech32 inj1... accounts) or Ethereum EIP-712 typed-data signing (0x... keys), with optional AuthZ grant delegation for session-based auto-signing.
Injective secures its APIs with none-public and signature-based-transactions across 4 declared security schemes, as derived from its OpenAPI definitions.
CompanyCryptoBlockchainDeFiTradingDerivativesWeb3Layer 1CosmosTokenizationPaymentsAI Agents
Methods: none-public, signature-based-transactions
Schemes: 4
OAuth flows:
API key in:
Security Schemes
public-read none
cosmos-signature transaction-signature
eip712-signature transaction-signature
authz-delegation on-chain-grant