Pangea Docs

Pangea provides two key features: Real-time and Historical data

Our data is fine-grained, open and shows every swap and position on Uniswap V2 and Uniswap V3 based DEXs.

Client Access

For early access you can apply here.

Credentials setup

You will have received a username and password. The examples in these docs export the following environment variables.

export PANGEA_USERNAME=<username>
export PANGEA_PASSWORD=<password>
export PANGEA_AUTH=$(echo -n "$PANGEA_USERNAME:$PANGEA_PASSWORD" | base64 -w 0)

Get started with our API

Currently, clients consume data from the API over HTTP or WebSockets with common data formats CSV, JSON and Arrow-IPC. See, API docs to get started

Ready to get started?

API

All API examples use curl. A WebSocket client will be released soon, please get in touch for early access.

For real-time use WebSockets API and for historical use HTTP or WebSockets API.

Make a request

curl -s --location --request GET \
    "https://app.pangea.foundation/v1/api/status" \
    --header "Accept: application/jsonstream" \
    --header "Authorization: Basic $PANGEA_AUTH" | jq -s

Status is the health endpoint for chains and toolboxes that contain availability, syncing and block height.

Result

[
    {
        "type": "Chain",
        "chain": 1,
        "chain_code": "ETH",
        "chain_name": "Ethereum",
        "service": "chain",
        "entity": "block",
        "latest_block_height": 17572170,
        "timestamp": 1687886916,
        "status": "Ok"
    },
    ...
]

All available chains and endpoints can be found by making a request to our /status endpoint, which should be called without any query parameters.

A chain parameter (?chain=ETH for example) is required for all other endpoints.
chain can also accept the EIP-155 chain ID 1 or our name Ethereum.

Support for multiple chains per request will be announced soon.

All requests default block filters on the latest block ?from_block=latest&to_block=latest. Set from_block to 1 to filter the whole chain ?from_block=1.

Filtering on other fields can be done directly on the field or by using a few conventions, using token0 as the example:

Filter directly by token0=0x....
Filter on a list by affixing __in comma separated by token0__in=0x1..,0x2...
Filter on a value greater than or equal to by affixing __gte
Filter on a value less than or equal to by affixing __lte

Response Format

Supported formats are JSON, JSON-LINES, CSV, Arrow-IPC

JSON is limited by block range, use JSON-LINES, CSV or Arrow-IPC for larger block ranges

Format can be specifed in two ways, by query parameter or Accept header. The query parameter takes precedence over Accept header.

?format=json_stream

--header "Accept: application/jsonstream"

Query parameter values

json, json_stream, csv, arrow

Accept headers

--header "Accept: text/csv"
--header "Accept: application/json"
--header "Accept: application/jsonstream"
--header "Accept: application/vnd.apache.arrow.stream"

Early Access

These datasets are currently in our Beta environment. If you would like early access you can apply here

Blocks

Block data is temporarily a subset of raw block data to be compatibile across EVMs. This will be updated with the introduction of new cross chain features.

curl -s --location --request GET \
    "https://app.pangea.foundation/v1/api/blocks?chains=ETH&from_block=-10&to_block=latest" \
    --header "Accept: application/jsonstream" \
    --header "Accept-Encoding: gzip" --compressed \
    --header "Authorization: Basic $PANGEA_AUTH" | jq

The First Immersive Web3 Environment