Noticing more credits being used than you expected? This guide explains what’s probably going on and how to handle it.
We believe in transparency around billing, and we want you to feel confident in how credits are being used.
Common Scenario: You Expected 1 Credit, But Were Charged 2
You may have set up your API request to be as minimal as possible—no optional enrichments, just the required URL.
However, the response still costs 2 credits instead of the expected 1.
Here’s why that can happen.
💡 The Role of “Data Freshness”
Enrich Layer includes a feature called Data Freshness, which ensures that the data you receive is fresh for up to 29 days—prioritizing accuracy and relevance.
When Data Freshness is enabled, your request:
Delivers the freshest possible data
Adds an extra credit charge
Even if you don’t ask for extra fields, Data Freshness runs independently, and can affect credit use.
⚙️ How to Check or Disable Data Freshness
You can manage this setting in your dashboard or through your API calls.
In the Dashboard:
Go to Settings.
Find the Data Freshness toggle.
Turn it off to avoid additional credit use.
In the API:
Make sure your call includes:
{
"url": "<company-profile-url>",
"use_cache": if-present
}
This ensures you’ll only be charged for a standard, 1-credit request.
Example Request With Minimal Credit Use
Here’s how to structure a lightweight API call:
{
"url": "<company-profile-url>",
"categories": "exclude",
"funding_data": "exclude",
"exit_data": "exclude",
"acquisitions": "exclude",
"extra": "exclude",
"use_cache": "if-present"
}
When Are Credits NOT Charged?
While most API requests cost 2 credits, there are specific scenarios where you won't be charged:
Zero-Cost Scenarios
You will not be charged credits in the following situations:
404 errors: If the profile URL returns a 404 error (profile doesn't exist, was deleted, or cannot be accessed)
Missing experience or education: If either the experience section OR the education section is completely missing from the profile, you will not be charged
Note: These policies ensure you only pay for valid profile data.
Thin or sparse profile data: If a profile exists but contains minimal information across most fields (only basic details like name and headline, with most other sections empty or null), you will not be charged. This can happen due to privacy settings, incomplete profiles, or data source limitations. The API will return a 200 success status, but with limited populated fields.
Profile Not Found (404 Errors):
If a profile doesn't exist or has been deleted, you'll receive a 404 error response and you will not be charged any credits.
This happens when:
- The profile URL is incorrect or contains typos
- The user has deleted their account
- The profile doesn't exist
💡 Tip: Use `use_cache: if-present` (shown above) to check cached data first before making a fresh request. This helps you avoid unnecessary API calls and manage your credit usage efficiently.
Can I Get a Credit Refund?
We know unexpected charges can be frustrating. If you’re unsure why a request cost more, feel free to reach out to our team.
We’re happy to investigate, explain any discrepancies, and review credit reimbursement requests on a case-by-case basis—especially if you were unaware of the setting.
👉 Contact support at [email protected] or click the chat icon in the bottom-right corner of the page.
📌 A Few Things to Keep in Mind
An additional 1 is charged on top of the base cost when Data Freshness is enabled, even if other enrichments are excluded.
Disable Data Freshness to keep calls to 1 credit.
Still Need Help?
We’re always here to help! Whether you’re just getting started with Enrich Layer or switching from another platform, our support team is ready to make everything smooth and easy.