Developer Guide

Rebar Data provides access to two services — Rebar API (REST) and Rebar RPC (JSON-RPC) — through a unified authentication system using API keys. This guide outlines how to request access and use your key to authenticate requests.

Getting Access

To begin using Rebar Data, you'll need an API key issued by Rebar Labs. Access is currently gated to ensure stability and proper resource allocation across the network.

To request access:

• Visit rebarlabs.io/contact and fill out the contact form mentioning API key access

• Include your project name, expected usage, and contact information

• Our team will review and issue credentials within 3 business days

Once approved, you’ll receive a unique API key associated with your account.

Authentication Format

For Rebar API (REST): Include your API key using the X-API-Key header:

X-API-Key: <your-api-key>

Example request:

GET /v1/brc20/balance?address=bc1...  
Host: api.rebarlabs.xyz  
X-API-Key: <your-api-key>

For Rebar RPC (JSON-RPC): Use the standard Authorization header with Bearer token format:

Authorization: Bearer <your-api-key>

Example request:

POST / HTTP/1.1  
Host: rpc.rebarlabs.xyz  
Authorization: Bearer <your-api-key>  
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "method": "getblockchaininfo",
  "params": [],
  "id": 1
}

Key Management Best Practices

• Keep your API key secure. Never expose it in public repos or client-side applications.

• Use environment variables or secret managers to store keys in production systems.

• Rotate keys periodically and regenerate them immediately if compromised.

• Respect usage limits. Default rate limits apply; contact us for custom plans.

What’s Next?

With your API key set up, you’re ready to start integrating with Rebar Data. Explore the full capabilities of each interface:

• Rebar API Reference
• Rebar RPC Reference