---
title: "Celo API"
description: "Celo Core RPC API over HTTPS and WSS"
url: "https://blockreq.com/docs/build/api-reference/celo/"
---

# Celo API

Celo endpoints use the EVM JSON-RPC Core API over HTTPS and WSS.

## Endpoint

| Item | Value |
| --- | --- |
| Network | Celo Mainnet |
| Protocol | EVM JSON-RPC 2.0 |
| Chain ID | `42220` (`0xa4ec`) |
| Public HTTPS | `https://celo-rpc.blockreq.com/v1/rpc/public` |
| Private HTTPS | `https://celo-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000` |
| Public WSS | `wss://celo-rpc.blockreq.com/v1/rpc/public` |
| Private WSS | `wss://celo-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000` |

These URLs use the product path `/v1/rpc` plus `/public` or `BRQ1P0000000000000000000000000000000000000000000000000000000`.

## Core Methods

Celo uses [EVM JSON-RPC Methods](https://blockreq.com/docs/build/api-reference/evm-methods/index.md) for `eth_*` reads and writes, archive-sensitive state calls, logs, and WSS subscriptions.

Old-block `eth_call` requires archive routing. BlockReq does not currently document or guarantee `eth_getProof`, `debug_*`, or `trace_*` on Celo.