How should I use the QIF 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.

QIF Format Hub

Quicken Interchange Format (.qif) files store account registers, split transactions, categories, and payee data in a plain-text financial export format. Despite its age, QIF still appears in legacy accounting and personal-finance imports. Use sample .qif files to test ledger imports, category mapping, split-transaction parsing, and compatibility with older bookkeeping or reconciliation systems.

Coverage Snapshot

CategoryData

Files3

Min Size0.1 KB

Max Size0.2 KB

Downloads (30d)16

Primary MIME Signals

application/octet-stream

Open Sample Page Open Manifest JSON

Related Formats in Data

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

Format Strategy Links

Open QIF FAQ

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.