RB2B OEM Partner API

The domain-management and usage API for RB2B OEM partners embedding RB2B identification inside their own platforms — POST /add_domain, POST /delete_domain, GET /domains and GET /credit_usage, authenticated with an Api-Key header issued on the OEM dashboard. The API is the ONLY supported way to authorize a domain: RB2B ignores traffic from any domain not added here, even when the OEM tracking script is installed. Credit usage returns credits_used with the last and next billing dates.

API entry from apis.yml

apis.yml Raw ↑
aid: rb2b:rb2b-oem-partner-api
name: RB2B OEM Partner API
tags:
- OEM
- Domain Management
- Partner
- Usage
- Billing
humanURL: https://support.rb2b.com/en/articles/12880800-using-the-rb2b-oem-program-api-webhook-guide
baseURL: https://app.rb2b.com/api/v1
description: 'The domain-management and usage API for RB2B OEM partners embedding RB2B identification
  inside their own platforms — POST /add_domain, POST /delete_domain, GET /domains and GET /credit_usage,
  authenticated with an Api-Key header issued on the OEM dashboard. The API is the ONLY supported way
  to authorize a domain: RB2B ignores traffic from any domain not added here, even when the OEM tracking
  script is installed. Credit usage returns credits_used with the last and next billing dates.'
properties:
- url: https://support.rb2b.com/en/articles/12880800-using-the-rb2b-oem-program-api-webhook-guide
  type: Documentation
- url: https://support.rb2b.com/en/articles/12579426-rb2b-s-oem-partner-program
  type: SignUp
- url: https://app.rb2b.com/oem_dashboard
  type: Portal
x-evidence:
  verified: '2026-08-12'
  method: live probe
  checks:
  - GET https://app.rb2b.com/api/v1/domains → 401 {"error":"missing_api_key"}
  - GET https://app.rb2b.com/api/v1/credit_usage → 401 {"error":"missing_api_key"}
  contract_source: Endpoints, request bodies and response shapes documented verbatim by RB2B in the OEM
    API & Webhook Guide.