Credit Consumption Model
B2B API Credit Consumption Model
Overview
This document explains how credits are consumed when using the Demandbase B2B API. Credit usage vaires by endpoint and billing model. The two primary models are Per Record Returned and Record Under Management (RUM)
Billing Models
Overview
The B2B API supports two billing models. Customers are assigned one of these models based on contract or SKU alignment.
Per Record Returned
Per Record Returned
- Credits are deducted each time a record is returned
- Common for real-time enrichment, CRM plugins, or UI-triggered workflows
Record Under Management (RUM)
- Credits are charged once per unique contact or company returned by a match call.
- Ideal for batch enrichment, synced databases, or CDP integrations.
- Subsequent fetches of the same record do not consume additional credits under this model.
Credit Costs by Endpoint (Per Record Returned Model)
Overview
In this model, a credit is deducted each time a record is returned. This includes direct API fetches for contact or company data, as well as supplemental assets like news or logos.
Cost Per Endpoint
| Endpoint | Credit Cost | Notes |
|---|---|---|
/contacts/search | 0 | Free to use; no credits charged |
/companies/search | 0 | Free to use; no credits charged |
/match | 1 per unique match | Based on number of unique contact/company IDs matched |
/contact/{contactId} | 1 | Includes contact and employment details |
/company/{companyId} | 1 | Includes firmographics; optional fields like familyTree and installedTech are included |
/company/{companyId}/newsfeed | 1 | Full news feed |
/company/{companyId}/news?categories= | 1 | Category-specific news |
/company/{companyId}/logos/size | 1 | Company logo image |
Bulk Match | 1 per match | Counted per unique matched record |
Bulk Fetch | 1 per record | Counted per contactId or companyId |
Technographics and Family Tree
Per Record Returned
Per Record Returned
- Credits are deducted each time a record is returned
- Common for real-time enrichment, CRM plugins, or UI-triggered workflows
Record Under Management (RUM)
- Credits are charged once per unique contact or company returned by a match call.
- Ideal for batch enrichment, synced databases, or CDP integrations.
- Subsequent fetches of the same record do not consume additional credits under this model.
Record Under Management (RUM)
- Credits are charged once per unique contact or company returned by a match call.
- Ideal for batch enrichment, synced databases, or CDP integrations.
- Subsequent fetches of the same record do not consume additional credits under this model.
Per Record Returned
- Credits are deducted each time a record is returned
- Common for real-time enrichment, CRM plugins, or UI-triggered workflows
Record Under Management (RUM)
- Credits are charged once per unique contact or company returned by a match call.
- Ideal for batch enrichment, synced databases, or CDP integrations.
- Subsequent fetches of the same record do not consume additional credits under this model.
QPS and Throughput
- The B2B API has default rate limits to ensure playform stability
- Standard QPS limit applies to all API keys.
- Contact your account manager for high QPS enablement
Updated 2 days ago