NDC SPL Data Elements: searching FDA other data

The other/nsde.json endpoint holds comprehensive ndc spl data elements file. We break down one working example and point out the parameters that matter.

November 30, 2025 · 5 min read · other/nsde.json

What this endpoint does

This article covers other/nsde.json, the openFDA route for NDC SPL Data Elements. Comprehensive NDC SPL data elements file. We are not the FDA — we just help you query their public API.

Who uses it

Historians, chemists, and data engineers dip into these supplementary files for substance identifiers, old press releases, and NDC reference material.

Example request

Paste this into a browser or our Explorer (swap the search term as needed):

GET https://api.fda.gov/other/nsde.json?search=_missing_:marketing_end_date&limit=5

You should see JSON with meta.results.total telling you how many matches exist.

Searching the data

Start with search=_missing_:marketing_end_date in our Explorer or your own HTTP client. Each endpoint documents its own field list on open.fda.gov. Common knobs: limit (how many rows), skip (offset for paging), sort (field:asc or field:desc), and count (aggregate unique values).

Tips that save time

If a query times out, tighten your search or lower limit. The public API is shared infrastructure.

limit — usually capped at 1,000 per call
skip — walk through large result sets
count=some_field.exact — quick frequency tables

Before you rely on this data

openFDA Explorer is an independent website. We are not affiliated with, endorsed by, or operated by the U.S. Food and Drug Administration (FDA).

FDA public data is useful for research and general interest. It is not medical advice. Talk to a qualified healthcare professional about your health. openFDA data may be incomplete or reported voluntarily — treat it as a starting point, not a verdict.