Guides
for everything Geocodio
Guides
Exporting your usage
Guides
for everything Geocodio
Exporting your usage
When you need your usage in a spreadsheet, the Usage page can export it as a CSV. Open the export dialog, pick a period and one of three shapes, and Geocodio builds the file for you.
How exports reach you
Exports run in the background, so you can close the page and carry on.
When the file is ready, Geocodio emails you a download link.
The export also appears under "Recent exports" in the export dialog for 7 days.
One row per day
One row for each day in the period, covering the whole account.
| Column | What it means | Example value |
|---|---|---|
| date (ET) | The day, in Eastern Time | 2026-09-02 |
| lookups | Lookups run that day | 31905 |
| fields | Data fields appended that day | 15200 |
| distance | Distance calculations run that day | 260 |
| included_credits | The day's included credits for the account | 25000 |
| billable_credits | The day's billable credits | 22365 |
Each lookup, appended data field and distance calculation uses one credit, so the lookups column alone is not what you are billed for. A day's included and billable credits add up to lookups + fields + distance.
A file of that shape looks like this:
| date (ET) | lookups | fields | distance | included_credits | billable_credits |
|---|---|---|---|---|---|
| 2026-09-01 | 12480 | 4120 | 0 | 16600 | 0 |
| 2026-09-02 | 31905 | 15200 | 260 | 25000 | 22365 |
| 2026-09-03 | 18402 | 6210 | 140 | 24752 | 0 |
One row per day and API key
The same daily view, split by key. One row for each combination of day and API key.
| Column | What it means | Example value |
|---|---|---|
| date (ET) | The day, in Eastern Time | 2026-09-02 |
| api_key | The API key the activity belongs to | 3f8c1a9d24b7e065 |
| api_key_owner | The team member the key belongs to | Priya Raman |
| lookups | Lookups that key ran that day | 28400 |
| fields | Data fields that key appended that day | 14100 |
| distance | Distance calculations that key ran that day | 260 |
| billable_credits | The key's billable credits for that day | 20120 |
No included credits in this shape
Included credits are a whole-account figure for the day, so they cannot be attributed to one API key. That is why this shape has no included_credits column.
A file of that shape looks like this:
| date (ET) | api_key | api_key_owner | lookups | fields | distance | billable_credits |
|---|---|---|---|---|---|---|
| 2026-09-01 | 3f8c1a9d24b7e065 | Priya Raman | 9800 | 3100 | 0 | 0 |
| 2026-09-01 | b62e40d7c98a1f53 | Tomas Berg | 2680 | 1020 | 0 | 0 |
| 2026-09-02 | 3f8c1a9d24b7e065 | Priya Raman | 28400 | 14100 | 260 | 20120 |
| 2026-09-02 | b62e40d7c98a1f53 | Tomas Berg | 3505 | 1100 | 0 | 2245 |
Every lookup
The most detailed shape, with one row per request.
| Column | What it means | Example value |
|---|---|---|
| time | When the lookup was recorded, in ISO 8601 with a UTC offset | 2026-09-03T09:14:22-04:00 |
| request_id | Identifier for the request the lookup belongs to | 8f31c2a04d |
| kind | What kind of request it was | geocode |
| status | How the request finished | success |
| input | The address text that was sent to Geocodio | 1109 Fairmount Ave, Baltimore, MD 21202 |
| countries | The countries the request matched, with a count for each | US:375;CA:3 |
| lookups | Lookups in the request | 378 |
| fields | Data fields appended | 756 |
| credits | Credits the request used | 1134 |
| accuracy_type | The accuracy type of the result | rooftop |
| accuracy_score | The accuracy score of the result | 1 |
| response_time_ms | The full time spent on the request, in milliseconds | 214 |
| api_key | The API key used | 3f8c1a9d24b7e065 |
| api_key_owner | The team member the key belongs to | Priya Raman |
This file contains your query data
The input column holds the address text you sent to Geocodio, so an every-lookup export carries your own query data. Store and share the file the way you would any other file of addresses. Geocodio Enterprise never stores the input you send, so on Enterprise this column is always empty.
A file of that shape looks like this:
| time | request_id | kind | status | input | countries | lookups | fields | credits | accuracy_type | accuracy_score | response_time_ms | api_key | api_key_owner |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-09-03T09:14:22-04:00 | 8f31c2a04d | geocode | success | 1109 Fairmount Ave, Baltimore, MD 21202 | US:1 | 1 | 2 | 3 | rooftop | 1 | 214 | 3f8c1a9d24b7e065 | Priya Raman |
| 2026-09-03T09:16:05-04:00 | 4b7e065a12 | batch geocode | success | 88 Rue Sherbrooke, Montreal, QC | US:375;CA:3 | 378 | 0 | 378 | 1980 | 3f8c1a9d24b7e065 | Priya Raman | ||
| 2026-09-03T09:21:48-04:00 | c98a1f5330 | geocode | returned nothing | 402 Cedar Hollow Ln, Lincoln, NE 68508 | US:1 | 1 | 0 | 1 | 96 | b62e40d7c98a1f53 | Tomas Berg |
Export limits
"Every lookup" covers at most the last 45 days, and each account can start one every-lookup export per day.
An export stops at 5,000,000 rows. When that happens, the last line of the file says so and suggests a narrower period.
Past months export without credit figures
In the daily shapes, exports of past months have empty credit columns. Those months come from Geocodio's monthly archive, which records activity rather than credit figures.
Who can export what
| Owner / Admin | Developer | Member | Billing | Read Only | Compliance | |
|---|---|---|---|---|---|---|
| One row per day | ||||||
| One row per day and API key | All keys | All keys | Own keys | |||
| Every lookup | All keys | All keys | Own keys |
"Own keys" means the API keys that person created. Owner and Admin exports include the api_key_owner column. A Developer export covers every key and keeps that column, but leaves it empty.
For what the tabs show on screen, see Understanding your usage page.