Credit Usage

SMARTe Enrichment APIs operate on a credit-based consumption model. Credits are associated with your organization and are evaluated for every enrichment request.

Credit validation occurs before enrichment processing begins. Credits are deducted only when enrichment data is successfully delivered.

How Credits Are Applied

Each request is evaluated independently. Credit deduction is tied to data delivery, not to request submission.

When Credits Are Deducted

Person enrichment returns enriched contact data
Company enrichment returns enriched company data
Specialized enrichment (email, mobile, technographics, funding) returns data
Any output mode returns one or more enrichment fields

When Credits Are Not Deducted

Authentication or Authorization fails
Input validation fails
The request is rate limited
The request is processed in audit-only (AUD) mode
No matching record is found
The response contains no enrichment data

Credit Validation

Before processing an enrichment request, SMARTe validates that sufficient credits are available for the organization. If insufficient credits are available:

The request is rejected
No enrichment processing occurs
An error response is returned

Credit Information in Responses

For successful enrichment requests, credit-related metadata is returned in the response headers. Typical headers include:

credits-deducted

Use the transaction identifier when auditing usage or contacting SMARTe Support.

Managing Credit Usage

To manage credit consumption effectively:

Use output modes to limit returned data
Avoid full enrichment when partial data is sufficient
Cache enrichment results where appropriate
Use audit-only mode to validate identifiers before enrichment

Credit allocation and replenishment are managed at the organization level.