Overview
Your API key is used to authenticate requests to RB2B APIs and track credit usage.
Every request must include your API key in the request header to verify your account and authorize access to the API suite.
⚠️ Important: Your API key is private and tied to your account. Do not share it publicly or include it in client-side code.
Accessing Your API Key
You can view your API key at any time from your RB2B APIs Dashboard.
Log in to your RB2B APIs Dashboard.
In the sidebar, click API Dashboard.
Your API key is listed under API Key.
Click Copy to securely copy it to your clipboard.
Using Your API Key in Requests
All authenticated requests must include your key in the header using the following format:
Key | Value | Add To |
Authorization |
| Header |
Content-Type |
| Header |
Example:
curl -X POST "https://api.rb2b.com/v1/fingerprint-to-hem" \ -H "Authorization: API-Key {{api_key}}" \ -H "Content-Type: application/json" \ -d '{"fingerprint": "example_fingerprint", "domain": "yourdomain.com"}'
Regenerating Your API Key
If your key has been compromised or you want to reset access, you can regenerate a new key at any time.
In your dashboard, click API Dashboard in the sidebar.
Locate your active key and click Regenerate Key 🔄.
Confirm the action when prompted.
Once regenerated:
The new key becomes active immediately.
The previous key stops working right away.
You'll need to update your integrations and any connected systems with the new key to prevent authentication errors.
💡 Tip: If you use your API key in multiple environments (e.g., production and staging), make sure to update each one before sending new requests.
Security Best Practices
Keep your API key secure to prevent unauthorized access and credit usage.
We recommend:
Never sharing your API key publicly or in screenshots.
Storing your key in a secure environment variable or vault.
Regenerating your key periodically or when team access changes.
Removing unused keys promptly if multiple keys are supported in the future.
Troubleshooting Authentication Errors
Common causes:
Missing or incorrect
AuthorizationheaderUsing an outdated or regenerated key
Attempting to use a key tied to a different account
Incorrect header format (should be
API-Key {{api_key}})
If you continue to receive authentication errors, verify your key in the API Key section of your dashboard and update any stored credentials.
Frequently Asked Questions
Are there rate limits for RB2B APIs?
There are no active rate limits on RB2B API endpoints today. This configuration may change, so it is smart to distribute requests efficiently rather than burst traffic.