Shadow
  • 🌗Overview
  • 🏁Quickstart
  • 🎯Use cases
  • ⛓️Supported chains
  • MODIFY CONTRACTS
    • Versioning
    • How to's
      • Proxy contracts
      • Using oracles
      • Factory contracts
      • Interdependent shadow contracts
  • GETTING DATA
    • Shadow RPC
    • Database syncs
    • Recurring exports
    • One-off exports
    • API Keys
  • Integrations
    • Postgres
    • GCS / S3
    • Dune
  • Product Guide
    • Catalog
    • Test runs
    • Subgraphs
  • Tips
    • Proxy contracts
    • Solidity beginners
      • Recommended tools
  • Resources
    • 📚Concepts
    • ❓FAQs
Powered by GitBook
On this page
Export as PDF
  1. GETTING DATA

API Keys

Learn how to authenticate your requests to Shadow.

PreviousOne-off exportsNextPostgres

Last updated 7 months ago

All API requests to Shadow are authenticated via API keys. This includes Shadow RPC requests, as well as api.shadow.xyz endpoints. You can create a new API key by going to your project’s settings page: .

Add your API key to the request header to authorize your Shadow API requests. This header must be included in every request.

X-SHADOW-API-KEY: <YOUR-API-KEY>

For example, this is how you’d authenticate a call to your Shadow RPC:

curl https://rpc.shadow.xyz/ethereum/mainnet/v1/<FORK>/<VERSION> \
  -X POST \
  -H "Content-Type: application/json" \
  -H "X-SHADOW-API-KEY: <YOUR-API-KEY>" \
  --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}'
https://app.shadow.xyz/settings