Can I convert government open-data JSON to Excel for investigative reporting?

Yes. Government open-data portals (data.gov, USASpending.gov, state and municipal portals) typically offer JSON downloads or API access. Save the JSON response and upload it to Deliteful. Each record becomes a row, with field names as column headers, ready for filtering and analysis.

Does this work with FEC, ProPublica, or Census API JSON?

Yes. The FEC API, ProPublica APIs, Census Bureau APIs, and similar public interest data sources return standard JSON arrays. Save the API response to a .json file and upload it. The output will be a structured Excel table matching the record fields.

What if the JSON has thousands of records?

Excel supports up to 1,048,576 rows per worksheet. Most public API responses and open-data downloads fall well within this limit. For very large datasets (full Census tables, multi-year spending records), filter at the API level before downloading or split large files before uploading.

Will nested fields like addresses or related entities appear in the output?

Yes, as text strings. Nested objects are serialized rather than silently omitted, so you can see that a field contains structured data even if it requires further processing to fully expand. This is useful for spotting linked entities or sub-records during initial review.

Does this support NDJSON from data journalism tools or data pipelines?

Yes. Newline-delimited JSON — one record per line — is fully supported. NDJSON is a common output format from scraping pipelines, streaming data tools, and some government bulk data downloads.

Convert Public API and Government JSON Data to Excel for Investigative Analysis

Public records, government open-data portals, and social platform APIs all deliver data in JSON — but investigative analysis, source cross-referencing, and story-supporting data work happens in Excel. Deliteful converts JSON datasets from any public API to structured spreadsheets in seconds, so you spend time on the story, not the data wrangling.

Create free account

Journalists and investigative researchers regularly pull JSON from sources like the FEC API, USASpending.gov, ProPublica Nonprofit Explorer, Census Bureau APIs, court record systems, and local government open-data portals. Getting those records into Excel for filtering, sorting, and pattern-finding is the first step in any data-driven investigation — and it shouldn't require a data editor or a Python script. Deliteful handles the conversion so reporters can work independently.

Each JSON object becomes a row; field names from the first record become column headers. The output is a flat, filterable Excel table ready for the kind of manual review that surfaces leads: sorting by dollar amount, filtering by date range, scanning for anomalies across hundreds or thousands of records. Nested fields are serialized to text rather than dropped, which preserves data that might otherwise be invisible during initial review.

How it works

1
Create your free account
Sign in with Google — no card required, takes about 3 clicks.
2
Pull your public data as JSON
Download or save the API response from your government portal, public database, or data source as a .json file.
3
Upload and convert
Deliteful processes the file and writes each record as a row with field names as column headers.
4
Analyze in Excel
Filter, sort, and cross-reference the records to identify patterns, outliers, and leads for your investigation.

Frequently asked questions

Can I convert government open-data JSON to Excel for investigative reporting?: Yes. Government open-data portals (data.gov, USASpending.gov, state and municipal portals) typically offer JSON downloads or API access. Save the JSON response and upload it to Deliteful. Each record becomes a row, with field names as column headers, ready for filtering and analysis.
Does this work with FEC, ProPublica, or Census API JSON?: Yes. The FEC API, ProPublica APIs, Census Bureau APIs, and similar public interest data sources return standard JSON arrays. Save the API response to a .json file and upload it. The output will be a structured Excel table matching the record fields.
What if the JSON has thousands of records?: Excel supports up to 1,048,576 rows per worksheet. Most public API responses and open-data downloads fall well within this limit. For very large datasets (full Census tables, multi-year spending records), filter at the API level before downloading or split large files before uploading.
Will nested fields like addresses or related entities appear in the output?: Yes, as text strings. Nested objects are serialized rather than silently omitted, so you can see that a field contains structured data even if it requires further processing to fully expand. This is useful for spotting linked entities or sub-records during initial review.
Does this support NDJSON from data journalism tools or data pipelines?: Yes. Newline-delimited JSON — one record per line — is fully supported. NDJSON is a common output format from scraping pipelines, streaming data tools, and some government bulk data downloads.

Create your free Deliteful account with Google and convert your next public data JSON download to an Excel investigation sheet in seconds.