Skip to main content

Can I See a Breakdown of My Credit Usage?

Written by Plinio Moraes
Updated over a month ago

Yes! You can view your API logs and credit usage directly from your Enrich Layer dashboard. This lets you see exactly how your credits are being used — broken down by request.

How to Access Your Usage Breakdown

  1. Log in to your Enrich Layer dashboard

  2. Navigate to the API Logs section

  3. You'll see a log of your API requests, including:

    1. Endpoint called — which API endpoint was used (e.g., Person Profile, Company Profile, Person Search)

    2. Credits used — total credits consumed by the request

    3. Credit Breakdown — a detailed breakdown showing exactly how much each parameter contributed to the final credit cost (e.g., base cost, Data Freshness, enrichment add-ons)

    4. Timestamp — when each request was made

    5. Response status — whether the request was successful or returned an error


Looking Up a Specific Request

Every API response includes a request ID in the response headers. You can use this ID to find the exact request in your API Logs and see its full credit breakdown.

This is especially useful when you want to verify how much a specific call cost or understand why it used more credits than expected.


What You Can Learn from Your Logs

The Credit Breakdown column is the most useful tool for understanding your charges. It shows you exactly which parameters added to the cost of each request. For example:

- Base cost — the standard credit charge for the endpoint

- Data Freshness — if enabled, this adds an extra credit per request

- Enrichment parameters — optional fields like `funding_data` or `exit_data` that increase the cost

- Result volume — for search endpoints, credits scale with the number of results returned (3 credits per result)


Tips for Monitoring Your Usage

- Check your credit balance regularly — Your remaining balance is visible on the dashboard

- Review logs after large queries — If you ran a batch of API calls, check the logs to confirm usage matches your expectations

- Set a smaller `page_size` when testing — This keeps per-call costs low while you iterate on search filters


Need Help Reading Your Logs?

If you're unsure what a specific charge means — or want help interpreting your credit breakdown — our support team is happy to assist. Just share the request ID from your response headers, and we can look into it together.


Reach out via in-app chat or email us at `[email protected]`.

Did this answer your question?