The RichAPI call log lists one row for every API call your workspace made. The log lives in the Recent Calls tab of the Usage & Credits page. Each row shows the endpoint, the time, the HTTP status, a Billable or Free badge, and the credits charged. Export CSV emails a file with one row per call for a range of up to 90 days.

This article covers the per-call log and the CSV export. For the credit formulas, the three billing models, and the GET /usage endpoint, read Tracking Credit Usage and Billing.

The call log is a tab inside the Activity section of the Usage & Credits page.

The page URL is /home/<workspace-slug>/usage. The log covers every API key in the workspace, not only the key you last used. Every member of the workspace can read the log and request an export. Reading the log and exporting it cost no credits.

The Recent Calls table shows six columns. Rows are sorted newest first.

Point at the value in the Called column to read the exact UTC timestamp of the call.

Details expands one row of the call log into six fields. A field with no value shows an em dash.

Cache hit and Your price are visible only here. Neither field ships in the CSV export.

The date range picker sits at the top right of the Usage & Credits page, beside Export CSV. The picker drives the call log, the charts, and the totals together. The default range is the last 30 days.

For a custom range, select a start date and an end date in the two-month calendar. A future date is not selectable.

CAUTION: A range longer than 90 days fails to load. The page shows Couldn't load usage for this range. Try again or pick a different range. Pick a shorter range.

The search box and the status control sit above the Recent Calls table. Both filters apply to the rows the page already loaded.

The search matches the system name, so enrich matches Enrich Profile and Enrich Profile matches nothing. Type one word, or type the name with underscores.

The call log loads at most 500 calls for the selected range. The table then shows 25 of those rows at a time.

The table shows no total for the range. The search box and the status control filter only those 500 loaded rows. For the complete set of calls, export the range to CSV.

A failure is a row with a red Status badge. RichAPI charges no credits for a failure, so the row also shows Free and 0 credits.

A row with a green status badge and a Free badge is not a failure. RichAPI records 0 credits for an asynchronous job status poll. It also records 0 credits for an email or phone lookup that found nothing. A per-result search with no base price and no results also costs 0.

The export produces one row per API call, oldest first. RichAPI builds the file in the background and emails a download link. Any member of the workspace can request an export.

The dialog opens with the date range the page currently shows. Change the range inside the dialog for a different period. The dialog range and the page range are independent.

CAUTION: An export range must not exceed 90 days. The dialog counts the days, disables Export, and shows Range is <n> days — exports are limited to 90 days. Pick a shorter range.

After you select Export, a message confirms the address the file goes to. The email arrives at the account email of the person who requested the export. RichAPI takes that address from your signed-in account, so an export never goes to a typed address.

The export dialog has two filters. Both filters apply only to a Filtered data export.

The dialog states this rule as well: only the endpoint filter and the billable filter apply to an export. The Search endpoint... text and the all / ok / error control in the call log do not carry over. To export a single endpoint, set it in the Endpoint filter.

RichAPI sends one email for every export request, for a success and for a failure alike.

WARNING: The download link is a password. Anyone who holds the link can download the file with no sign-in and no API key. Do not forward the email.

The export file holds these 11 columns, in this order, with one row per API call.

Rows run oldest first, because an export is a statement of a period. The file covers every API key in the workspace. Group by api_key_name to split the spend per key.

A cell that starts with =, +, -, @, a tab, or a carriage return arrives with a leading apostrophe. Excel and Google Sheets read such a cell as a formula, and the apostrophe marks it as text instead. The apostrophe is part of the protection, not part of your data.

The CSV carries the facts a customer needs to audit a charge. RichAPI leaves out three kinds of field on purpose.

credits holds the whole charge for each call. plan_credits shows the part of that charge that Enrichment Pass credits paid. At list price, multiply credits by 0.02 for the dollar value of a range.

A RichAPI invoice charges for credits you bought. The call log accounts for credits you spent. Reconciliation is therefore two comparisons, not one. Read the invoice in the Stripe billing portal, which opens from Manage Payment Method on the Plans & Billing page. Only an organization owner can open the billing portal.

The CSV sum and the dashboard total read the same stored rows, so a difference always has one of the causes below.

The RichAPI call log is the Recent Calls tab in the Activity section of the Usage & Credits page, at /home/<workspace-slug>/usage. The log shows one row per API call, newest first, for every API key in the workspace.

The call log loads at most 500 calls for the selected date range, and shows 25 of them at a time behind a Load more button. Export the range to CSV for every call.

The search box matches the system name of the endpoint, in lower case with underscores. enrich matches Enrich Profile, and Enrich Profile matches nothing. Type a single word, or type the name with underscores.

One export covers up to 90 days. The dialog counts the days, disables the Export button, and names the day count for a longer range. Request several exports to cover a longer period.

The file holds 11 columns in this order: called_at, api_name, api_key_name, status_code, billable, credits, job_id, request_id, latency_ms, result_count, plan_credits. credits holds the whole charge for each call.

No. credits is the charged amount. At list price, multiply credits by 0.02 for dollars, or read Your price in the Details panel of a call log row.

No. The export filters are Endpoint and Billable only. Export the range with All data in this range, then filter the CSV on status_code. A failed call always carries billable = False and credits = 0.

RichAPI emails the download link to the account email of the person who requested the export. Any workspace member can request one. The link works for 7 days with no sign-in, so treat it as a password.

Next: Transaction History, Receipts, and Payment Methods