Manifest Files for S3/GCS Drops

Manifest files are now generated for all signal data drops, enabling event-driven data pipelines.

After each data delivery, a manifest file is written to a dedicated manifest bucket. Each signal type gets its own manifest file per delivery date.

For full details on manifest location, schema, and usage, see our Manifest Files guide.

Quick Example

File: news_2026-04-07.json

{
  "signal_type": "news",
  "delivery_date": "2026-04-07",
  "status": "complete",
  "destination": "internal",
  "deliveries": [
    {
      "delivery_timestamp": "2026-04-07T00:00:00Z",
      "data_path": "gs://autobound-news-v3/2026-04-07-00-00-00/",
      "files": [
        {
          "file_name": "output.jsonl",
          "file_path": "gs://autobound-news-v3/2026-04-07-00-00-00/output.jsonl",
          "format": ".jsonl",
          "size_bytes": 79510730,
          "record_count": 16766
        },
        {
          "file_name": "output.parquet",
          "file_path": "gs://autobound-news-v3/2026-04-07-00-00-00/output.parquet",
          "format": ".parquet",
          "size_bytes": 39160557,
          "record_count": 16766
        }
      ],
      "record_count": 33532
    }
  ],
  "total_record_count": 33532,
  "total_file_count": 2,
  "pipeline_run_id": null,
  "created_at": "2026-04-07T14:36:33Z"
}