> ## Documentation Index
> Fetch the complete documentation index at: https://www.forager.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Forager is a REST API for B2B people, company and job post data: contact lookups (phone numbers, personal emails, work emails), person, company and job post search, and bulk data feeds.
> Server: https://api-v2.forager.ai. Send the API key in the X-API-KEY header. Most paths include {account_id}. Read FORAGER_API_KEY and FORAGER_ACCOUNT_ID from the environment; never put the key in client-side code, logs or prompts.
> To add Forager to a project, follow https://www.forager.ai/docs/guides/agent-quickstart.md. To pick an endpoint, read https://www.forager.ai/docs/guides/choose-an-endpoint.md. For end-to-end builds, see https://www.forager.ai/docs/recipes/overview.md.
> Most requests spend credits. Do not guess costs; use https://www.forager.ai/docs/api-overview/credit-pricing.md and ask the user before spending credits.
> Use only endpoints and fields defined in https://www.forager.ai/docs/openapi.yaml. Forager has no MCP server for the API yet; the /mcp endpoint on this site searches the documentation only.

# Output Data File Details

> Output file details for Forager data feeds: file locations, formats (CSV, JSON, Parquet), encoding and example files.

![Data feed file format: feed files delivered as CSV, JSON or Parquet under a dated path](https://mintcdn.com/forager/EGsWCxLOYv1Cb__c/images/illustrations/data-feed-file-format-csv-json-parquet.svg?fit=max\&auto=format\&n=EGsWCxLOYv1Cb__c\&q=85\&s=35f114a4a849eab6e94aa89156142352)

The following table describes the general details for the output files generated by Forager:

| **Feature** | **Supported** | **Notes** |
| - | - | - |
| **Location of files** | **Files in Amazon S3** | Files can be unloaded directly to any user-supplied bucket in S3, then can be downloaded locally using AWS utilities. |
| | **Files in Google Cloud Storage** | Files can be unloaded directly to any user-supplied container in Cloud Storage, then can be downloaded locally using Cloud Storage utilities. |
| | **Files in Microsoft Azure** | Coming soon. |
| **File formats** | **Delimited files (CSV, TSV, etc.)** | Any valid delimiter is supported; default is comma (i.e. CSV). |
| | **JSON** | |
| | **Parquet** | |
| **File encoding** | **UTF-8** | Output files are always encoded using UTF-8, regardless of the file format; no other character sets are supported. |

### Example file

Person NDJSON file: [data\_0\_0\_0.ndjson](https://www.forager.ai/docs/assets/data_0_0_0.a7202234296aa8827cf5fceb406c6a9652070a7cdf9fc58a11989f741438f15d.4478b203.ndjson)

Organization NDJSON file: [data\_0\_0\_0.ndjson](https://www.forager.ai/docs/assets/data_0_0_0.e53d1e8a62550356ab29cf061fa91833b8891263c2538fee005e1c0d86cc1524.46e9c3c3.ndjson)

## Row format

Each record in an NDJSON file is one JSON object with these top-level fields (see the example files above):

| Field | Description |
| - | - |
| `id` | Forager record ID (integer). |
| `date_updated` | When the record was last crawled, for example `2026-07-24 22:42:18.804 Z` (UTC). |
| `schema_version` | Schema version of `serialized_data`, for example `2.0.4`. |
| `serialized_data` | The record itself, as described in the [schema](https://www.forager.ai/docs/data-license/v2/schema.md) for the feed type and schema version. |

## File paths & names

File paths are constructed as so:

```
/forager_data_feed/<data_feed_id>/<date_created>/<data_feed_type>_<schema_version>/data_<partition_id>.<file_type>.<compression_type>

# Example:
/forager_data_feed/123/2025-10-15/person_2.0.4/data_0_0_1.json.gzip
```

Where the above variables represent:

* `data_feed_id`: A Forager provided data feed ID, provide by our support team.
* `data_feed_type`: Possible options are; `person`, `organization`, or `job`.
* `schema_version`: Forager schema version that represents the versioning of serialized data for data feed type, this will be provided by your customer support rep.
* `date_created`: Date when the export was created, Ex: `2025-10-16`.
* `partition_id`: Partition column values generated when exporting your files, Ex: `0_0_0`, `0_0_1`, etc.
* `file_type`: This will be one of the following options; `json`, `csv`, `tsv`, `parquet`.
* `compression_type`: This will be one of the following options; `gzip`, `bz2`, `brotli`, `zstd`.

Change the feed, format or compression to see where a file lands:

The file lands at

<pre />

## Serialized Data Schema

[Schema located here.](https://www.forager.ai/docs/data-license/v2/schema.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.