How should I use the AVRO manifest endpoint?

Fetch manifest JSON to pin fixture names, sizes, hashes, and MIME expectations in automated tests.

Why does this format have a category-specific hub?

A category-specific hub keeps assumptions aligned with practical workflows and related format alternatives.

Format reference

AVRO Format Hub

Avro (.avro) files store schema-aware binary records commonly used in event streams and data pipelines. Use sample Avro files to validate schema evolution, nullable fields, and record-batch ingestion.

Open Sample Page Open Manifest JSON

3 Files

201 Downloads (30d)

application/octet-stream

Related Formats in Data

AVRO Related Formats

SQL (14) YAML (10) ENV (9) GRAPHQL (9) INI (9) JSONL (9) NDJSON (9) PROTO (9)

Format Strategy Links

AVRO Format Guides

Open AVRO FAQ

Implementation Notes

AVRO Implementation Notes

Use the manifest endpoint for deterministic fixture selection in CI, then validate MIME/type detection against actual parser output.

If this format appears in multiple categories, prefer category-specific hub pages to keep test assumptions aligned with real usage.