A smaller API response can break a research pipeline.
Databento separates batch-job summaries from full details. A small change at the boundary can travel a long way.
What changed
Databento announced that batch.list_jobs would return only id, state and ts_received. Full information moves to batch.get_job_details. The vendor describes this as a breaking change for consumers of the removed fields.
The markets connection
Our reading: a research pipeline depends on interface contracts as well as market data. Code that polls job lists may also use fields for progress, costs or downstream decisions. Test that boundary explicitly.
Where to look
Find each consumer of the job-listing response, identify which fields it reads, and consult the current vendor notice for migration instructions and transition dates.
Keep it in context
This is a dated vendor announcement. It does not establish whether your integration is affected or whether a transition is still open.
Upcoming changes to the historical batch API Databento · 26 August 2026Article history
- 18 September 2026 — First web edition. Announcement and source link checked.