Demandbase Rate Limits
Demandbase publishes per-API rate limits on its developer portal. The B2B API is limited by requests per minute plus a hard concurrency cap on asynchronous jobs; the Data Export API is limited per endpoint per day plus a daily volume ceiling and a single-concurrent-job rule; the Data Import API is limited per endpoint per day plus a file-size ceiling. All three answer HTTP 429 on exhaustion. Demandbase documents no RateLimit-* or X-RateLimit-* response headers and no Retry-After on any surface, so a client cannot read its remaining budget from a response — it must track consumption itself or poll the Usage API. Credits are a separate, orthogonal entitlement from rate limits.
Demandbase Rate Limits is the machine-readable rate-limit profile for Demandbase on the APIs.io network, in the API Commons Rate Limits shape.
It captures 15 rate-limit definitions.
Limit state is signalled in the request, response, retry_after, and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, concurrencyExceeded, and serviceUnavailable.
Tagged areas include Account-Based Marketing, B2B Marketing, Data Enrichment, Intent Data, and Rate Limiting.
requestresponseretry_afternote
Limits
Sources
- https://developer.demandbase.com/docs/b2b-rate-limits
- https://developer.demandbase.com/docs/rate-limits
- https://developer.demandbase.com/docs/rate-limits-1
- https://developer.demandbase.com/docs/handling-errors
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.