Catalog / DailyMed SPL Web Services

DailyMed SPL Web Services API

dailymed.nlm.nih.gov

Read-only JSON access to DailyMed SPL list, label detail, and version-history resources. The list resource is live and source-paginated. DailyMed returns only set IDs, titles, and publication dates in list records; document identity, product, ingredient, labeler, and effective-date fields are populated by the XML detail resource. The requested updated_since filter is mapped to DailyMed's documented published_date >= comparison.

  • health
  • drug-labels
  • DailyMed
  • SPL
3 endpointsDocs updated

Endpoint health

Loading verification…

Connect your agent

Connect through MCP so your agent can find this API, read its docs, and call its endpoints.

Setup guide

Add the server from your terminal.

Claude Code · terminal
claude mcp add --transport http agent-data https://agent-data.motie.dev/mcp

In Claude Code, run /mcp, select agent-data, then Authenticate. Sign in to your agent-data account in the browser.

Then ask your agent to use the DailyMed SPL Web Services API for your task.

Call it over HTTP

Get an API key

Sign up free, generate an API key, and set it as AGENT_DATA_API_KEY in your environment. Your first 100 calls each month are free.

Lists current SPL resources from DailyMed. ingredient and brand are mapped to DailyMed's drug_name filter with name_type generic or brand. updated_since is mapped to published_date with the documented gte comparison. cursor is the source page number returned in next_cursor. List rows retain nullable detail-only fields because DailyMed's JSON list carries setid, title, publication date, and version but not the SPL document id or product fields.

Optional parameters 4

Generic/ingredient name, as accepted by DailyMed drug_name.

Brand name, as accepted by DailyMed drug_name.

Return SPLs published on or after this date; mapped to published_date gte.

DailyMed page number returned as next_cursor; omit for page 1.

View call pricing
cURL · Labels
curl --request GET --get 'https://3kpkg0jfvk.execute-api.us-east-2.amazonaws.com/prod/bd80f521-6d5b-4ed5-b70f-d9e603578105/labels' \
  --header "Authorization: Bearer $AGENT_DATA_API_KEY"

Endpoints

Inputs and response fields for every endpoint in this API.

GETLabels/labels

Lists current SPL resources from DailyMed. ingredient and brand are mapped to DailyMed's drug_name filter with name_type generic or brand. updated_since is mapped to published_date with the documented gte comparison. cursor is the source page number returned in next_cursor. List rows retain nullable detail-only fields because DailyMed's JSON list carries setid, title, publication date, and version but not the SPL document id or product fields.

Input

ingredientOptionalQuery · string | null

Generic/ingredient name, as accepted by DailyMed drug_name.

Example: menthol

brandOptionalQuery · string | null

Brand name, as accepted by DailyMed drug_name.

Example: EAGLE BRAND

updated_sinceOptionalQuery · string (date) | null

Return SPLs published on or after this date; mapped to published_date gte.

Example: 2026-10-01

cursorOptionalQuery · string | null

DailyMed page number returned as next_cursor; omit for page 1.

Response

dataobject[]
data[].title?string | null
data[].set_idstring
data[].labeler?string | null
data[].version?integer | null
data[].label_id?string | null
data[].brand_name?string | null
data[].source_urlstring
data[].observed_atstring
data[].spl_version?integer | null
data[].document_url?string | null
data[].generic_name?string | null
data[].source_as_of?string | null
data[].effective_date?string | null
data[].published_date?string | null
metadataobject
metadata.next_page?integer | null
metadata.source_urlstring
metadata.next_cursor?string | null
metadata.total_pages?integer | null
metadata.current_page?integer | null
metadata.source_as_of?string | null
metadata.previous_page?integer | null
metadata.total_elements?integer | null
metadata.previous_cursor?string | null

Fields marked ? are optional.

For the next page, pass next_cursor from the response as cursor. Leave it empty on the first call.

GETLabels by label id/labels/{label_id}

Returns one SPL detail record. DailyMed's REST detail resource is addressed by SET ID, so this path accepts the set_id returned by /labels (despite the requested label_id path name). The response's label_id is the SPL XML document id and set_id is its stable set identifier.

Input

label_idRequiredPath · string

DailyMed SET ID from a list result; returned in the set_id field.

Example: 107eed24-d1a5-429e-b388-fad8879e9ca4

Response

title?string | null
set_idstring
labeler?string | null
version?integer | null
label_id?string | null
brand_name?string | null
source_urlstring
observed_atstring
spl_version?integer | null
document_url?string | null
generic_name?string | null
source_as_of?string | null
effective_date?string | null
published_date?string | null

Fields marked ? are optional.

GETLabels by set id versions/labels/{set_id}/versions

Returns DailyMed's version history for the supplied set ID. The source history resource returns version and publication date; detail-only fields are nullable, and document_url is null because the source supplies no version-specific document URL.

Input

set_idRequiredPath · string

DailyMed SPL set ID.

Example: 107eed24-d1a5-429e-b388-fad8879e9ca4

Response

dataobject[]
data[].title?string | null
data[].set_idstring
data[].labeler?string | null
data[].version?integer | null
data[].label_id?string | null
data[].brand_name?string | null
data[].source_urlstring
data[].observed_atstring
data[].spl_version?integer | null
data[].document_url?string | null
data[].generic_name?string | null
data[].source_as_of?string | null
data[].effective_date?string | null
data[].published_date?string | null
metadataobject
metadata.next_page?integer | null
metadata.source_urlstring
metadata.next_cursor?string | null
metadata.total_pages?integer | null
metadata.current_page?integer | null
metadata.source_as_of?string | null
metadata.previous_page?integer | null
metadata.total_elements?integer | null
metadata.previous_cursor?string | null

Fields marked ? are optional.

Don’t see the endpoint you need?

Ask agent-data to add an endpoint or return more fields. Extensions are free and keep existing endpoints working.