Can I convert PubMed or other academic API JSON responses to Excel?

Yes. PubMed E-utilities, Semantic Scholar, OpenAlex, and most academic data APIs return JSON arrays or paginated JSON objects. Save the response to a .json file and upload it to Deliteful. Each article or record becomes a row, with metadata fields as columns.

Will the output work for qualitative coding in Excel?

Yes. The flat table output — one record per row, named columns — is the standard input format for qualitative coding workflows in Excel, including intercoder reliability sheets and thematic tagging grids. Add your coding columns to the right of the converted data.

What happens to nested fields like author arrays or keyword lists?

Nested arrays and objects are converted to their text representation in the cell. For example, an authors array might appear as a JSON string in one cell. If you need each author as a separate row or column, flatten the JSON upstream before uploading — this is typically a one-time preprocessing step per dataset.

Is NDJSON from data repositories supported?

Yes. Some repositories and export tools produce newline-delimited JSON (one object per line). Deliteful supports both standard JSON arrays and NDJSON, so most research data download formats are covered.

Can I use the Excel output to import data into SPSS or Stata?

Yes. Both SPSS and Stata import .xlsx files directly. The flat table structure Deliteful produces — consistent column headers, one case per row — is the format both tools expect for data import.

Convert Research API and Repository JSON to Excel for Analysis

Research datasets from PubMed, figshare, government open-data portals, and survey APIs arrive in JSON — but qualitative coding, statistical prep, and collaborator review all happen in Excel or SPSS-ready spreadsheets. Deliteful converts your JSON dataset to a structured .xlsx in seconds, without writing a single line of R or Python just to reformat the file.

Create free account

Academic researchers increasingly pull data directly from REST APIs — PubMed E-utilities, OSF, Zenodo, ICPSR, Census Bureau APIs, Twitter/X Academic Research access — and the response format is almost always JSON. Getting that into Excel for initial coding, variable review, or hand-off to a collaborator who doesn't work in code requires a conversion step that shouldn't take 20 minutes. Deliteful makes it a single upload.

The tool writes each JSON object as one row and derives column headers from the keys in the first record. For dataset records that are structurally consistent — which most well-formed research API responses are — the output is a clean, flat table ready for coding schemes, frequency counts, or import into SPSS and Stata. Nested sub-objects are serialized to text, making them visible for inspection even if they require further flattening for analysis.

How it works

1
Sign in free
Create your Deliteful account with Google OAuth — no card required, about 3 clicks.
2
Export your dataset as JSON
Save the API response or repository download as a .json file on your computer.
3
Upload and convert
Upload the file to Deliteful; each record is written as a row with field names as column headers.
4
Open in Excel for analysis
Use the .xlsx for coding, filtering, or import into your statistical software of choice.

Frequently asked questions

Can I convert PubMed or other academic API JSON responses to Excel?: Yes. PubMed E-utilities, Semantic Scholar, OpenAlex, and most academic data APIs return JSON arrays or paginated JSON objects. Save the response to a .json file and upload it to Deliteful. Each article or record becomes a row, with metadata fields as columns.
Will the output work for qualitative coding in Excel?: Yes. The flat table output — one record per row, named columns — is the standard input format for qualitative coding workflows in Excel, including intercoder reliability sheets and thematic tagging grids. Add your coding columns to the right of the converted data.
What happens to nested fields like author arrays or keyword lists?: Nested arrays and objects are converted to their text representation in the cell. For example, an authors array might appear as a JSON string in one cell. If you need each author as a separate row or column, flatten the JSON upstream before uploading — this is typically a one-time preprocessing step per dataset.
Is NDJSON from data repositories supported?: Yes. Some repositories and export tools produce newline-delimited JSON (one object per line). Deliteful supports both standard JSON arrays and NDJSON, so most research data download formats are covered.
Can I use the Excel output to import data into SPSS or Stata?: Yes. Both SPSS and Stata import .xlsx files directly. The flat table structure Deliteful produces — consistent column headers, one case per row — is the format both tools expect for data import.

Create your free Deliteful account with Google and convert your next research API dataset from JSON to Excel in seconds.