> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/openfda.md).

# OpenFDA

Search public FDA drug, device, and food datasets.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| OpenFDA   | API Key        |

#### OpenFDA

Connect with an openFDA API key for higher request quotas.

**Set up in OpenFDA**

1. Prepare the OpenFDA account or service that the workflow will access. Grant access to the required resources and operations.
2. Create or obtain the API credential identified in the fields below. Use the provider instructions linked with those fields to find its key-management page.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **OpenFDA**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                  |
| ------------- | -------- | ---------------------------------------------------------------------------------------------- |
| API Key       | Yes      | Your free openFDA API key. [Provider instructions](https://open.fda.gov/apis/authentication/). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **OpenFDA** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Search drug adverse events

Search public FDA drug adverse-event reports.

**Inputs**

| Field           | Type    | Required | Description                                                                              |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| Search query    | string  | Yes      | The adverse-event field and value to find.                                               |
| Maximum results | integer | No       | The maximum number of matching records to return. Minimum: 1. Maximum: 100. Default: 10. |
| Skip            | integer | No       | Continue from an earlier OpenFDA result offset. Minimum: 0. Maximum: 25000. Default: 0.  |

**Outputs**

| Field                 | Type          | Description                                             |
| --------------------- | ------------- | ------------------------------------------------------- |
| Total matches         | integer       | The total matching reports OpenFDA found.               |
| Adverse-event reports | object\_array | The matching drug adverse-event reports.                |
| Next skip             | integer       | Pass this back as Skip to continue the search.          |
| Truncated             | boolean       | Whether OpenFDA's offset limit prevents further paging. |

#### Search drug labeling

Search public FDA drug labeling.

**Inputs**

| Field           | Type    | Required | Description                                                                              |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| Search query    | string  | Yes      | The drug-label field and value to find.                                                  |
| Maximum results | integer | No       | The maximum number of matching records to return. Minimum: 1. Maximum: 100. Default: 10. |
| Skip            | integer | No       | Continue from an earlier OpenFDA result offset. Minimum: 0. Maximum: 25000. Default: 0.  |

**Outputs**

| Field         | Type          | Description                                             |
| ------------- | ------------- | ------------------------------------------------------- |
| Total matches | integer       | The total matching labels OpenFDA found.                |
| Drug labels   | object\_array | The matching drug labels.                               |
| Next skip     | integer       | Pass this back as Skip to continue the search.          |
| Truncated     | boolean       | Whether OpenFDA's offset limit prevents further paging. |

#### Search device recalls

Search public FDA medical-device recalls.

**Inputs**

| Field           | Type    | Required | Description                                                                              |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| Search query    | string  | Yes      | The device-recall field and value to find.                                               |
| Maximum results | integer | No       | The maximum number of matching records to return. Minimum: 1. Maximum: 100. Default: 10. |
| Skip            | integer | No       | Continue from an earlier OpenFDA result offset. Minimum: 0. Maximum: 25000. Default: 0.  |

**Outputs**

| Field          | Type          | Description                                             |
| -------------- | ------------- | ------------------------------------------------------- |
| Total matches  | integer       | The total matching device recalls OpenFDA found.        |
| Device recalls | object\_array | The matching medical-device recalls.                    |
| Next skip      | integer       | Pass this back as Skip to continue the search.          |
| Truncated      | boolean       | Whether OpenFDA's offset limit prevents further paging. |

#### Search food enforcement reports

Search public FDA food enforcement reports.

**Inputs**

| Field           | Type    | Required | Description                                                                              |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| Search query    | string  | Yes      | The food-enforcement field and value to find.                                            |
| Maximum results | integer | No       | The maximum number of matching records to return. Minimum: 1. Maximum: 100. Default: 10. |
| Skip            | integer | No       | Continue from an earlier OpenFDA result offset. Minimum: 0. Maximum: 25000. Default: 0.  |

**Outputs**

| Field                    | Type          | Description                                                |
| ------------------------ | ------------- | ---------------------------------------------------------- |
| Total matches            | integer       | The total matching food enforcement reports OpenFDA found. |
| Food enforcement reports | object\_array | The matching food recall and enforcement reports.          |
| Next skip                | integer       | Pass this back as Skip to continue the search.             |
| Truncated                | boolean       | Whether OpenFDA's offset limit prevents further paging.    |

#### Search drug NDC directory

Search the public National Drug Code directory.

**Inputs**

| Field           | Type    | Required | Description                                                                              |
| --------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| Search query    | string  | Yes      | The NDC field and value to find.                                                         |
| Maximum results | integer | No       | The maximum number of matching records to return. Minimum: 1. Maximum: 100. Default: 10. |
| Skip            | integer | No       | Continue from an earlier OpenFDA result offset. Minimum: 0. Maximum: 25000. Default: 0.  |

**Outputs**

| Field         | Type          | Description                                                |
| ------------- | ------------- | ---------------------------------------------------------- |
| Total matches | integer       | The total matching NDC products OpenFDA found.             |
| NDC products  | object\_array | The matching products in the National Drug Code directory. |
| Next skip     | integer       | Pass this back as Skip to continue the search.             |
| Truncated     | boolean       | Whether OpenFDA's offset limit prevents further paging.    |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/openfda.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
