Appearance
Choose an Access Path
DataBee APIs are available through the Direct Gateway or RapidAPI Hub. Both routes reach the same API contract; choose one based on where you want to manage keys, billing, and quotas.
Recommended for new integrations
Use the Direct Gateway at https://api.databee.dev. It offers the lowest-friction setup, free credits, credit rollover, and direct support. RapidAPI details are included below for teams already standardized on that marketplace.
Direct Portal Access (Developer DataBee)
- Base URL:
https://api.databee.dev - Developer Console: https://console.databee.dev
- Authentication: Generate a free API key at https://console.databee.dev and pass via
Authorization: Bearer YOUR_DATABEE_API_KEY.
RapidAPI Access
If you prefer to integrate via RapidAPI, use the trademark-free SiteAtlas listing:
SiteAtlas API (siteatlas.p.rapidapi.com)
- Base URL:
https://siteatlas.p.rapidapi.com - Host Header:
x-rapidapi-host: siteatlas.p.rapidapi.com
Legacy listing
The similarweb-api-pro.p.rapidapi.com listing is retained for existing integrations only and may be removed by RapidAPI because of trademark policies. Similarweb has previously taken down API listings for trademark-related reasons, so this is a long-term availability risk even if you already use that listing's v2 endpoints. Do not start new integrations against it; migrate to siteatlas.p.rapidapi.com when possible.
For endpoint and response-shape changes, see the v1 to v2 migration guide.
RapidAPI Specific Request Headers
When calling via RapidAPI, include the RapidAPI proxy headers (x-rapidapi-host and x-rapidapi-key):
http
x-rapidapi-host: siteatlas.p.rapidapi.com
x-rapidapi-key: YOUR_RAPIDAPI_KEYLegacy authentication
Some older marketplace routes also require Authorization: Bearer YOUR_DATABEE_API_KEY. If you maintain an existing legacy integration, keep that header until you migrate; new SiteAtlas subscriptions should use the RapidAPI headers above.
Legacy RapidAPI listing (migration only)
Existing users of similarweb-api-pro.p.rapidapi.com can continue using its current base URL and host header while migrating. The response body is the same as the SiteAtlas listing, but the listing itself is not recommended for new work.
Comparison Matrix
| Feature | Direct Portal (console.databee.dev) | RapidAPI Marketplace |
|---|---|---|
| Pricing & Cost | Save up to 40% on credit pricing | Standard marketplace pricing |
| Free Credits | 500 Free Credits (100 recurring monthly + 400 trial credits on sign-up) | No free credits included |
| Credit Validity | Credits remain valid for up to 12 months | Monthly plan with no credit rollover |
| Billing Precision | Only successful requests are charged | Charged against plan & overage rules |
| On Cancellation | Credits remain active in your wallet for up to 12 months | Unused quota is deleted instantly |
| Support & Refunds | Direct 24/7 provider support & instant credit restoration | Support responses take 3–4 business days |
| Listing Risk | Permanent direct provider SLA | Listings can be removed due to marketplace policies |
Code Examples
bash
curl -X GET "https://api.databee.dev/siteatlas/site-overview?url=github.com" \
-H "Authorization: Bearer YOUR_DATABEE_API_KEY"bash
curl --request GET \
--url 'https://siteatlas.p.rapidapi.com/site-overview?url=github.com' \
--header 'Content-Type: application/json' \
--header 'x-rapidapi-host: siteatlas.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY'bash
curl --location 'https://similarweb-api-pro.p.rapidapi.com/site-overview?url=microsoft.com' \
--header 'x-rapidapi-host: similarweb-api-pro.p.rapidapi.com' \
--header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY' \
--header 'Authorization: Bearer YOUR_DATABEE_API_KEY'javascript
const response = await fetch('https://siteatlas.p.rapidapi.com/site-overview?url=github.com', {
headers: {
'x-rapidapi-host': 'siteatlas.p.rapidapi.com',
'x-rapidapi-key': 'YOUR_RAPIDAPI_KEY'
}
});
const data = await response.json();