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

# Embase Integration

Connect Embase to search licensed content and add records to your nests.

The **Embase** integration lets you search Embase and add records to a nest through **Automatic Search**. It requires Elsevier credentials and an eligible Embase subscription.

{% hint style="warning" %}
**An Embase subscription is not included in your Nested Knowledge license.** You will need to acquire this separately.
{% endhint %}

### Subscription Requirements

Elsevier does not include the Embase API in its free-access tier. Your organization needs an Embase subscription. Commercial organizations also need an active API subscription through their Elsevier Account Manager.

If you are unsure of your subscription status, contact your Elsevier Account Manager or institutional librarian.

### Connect Embase

An **Organization Owner** or **Admin** connects **Embase** once for the organization. The integration is then available in every nest the organization owns.

1. In [**Organization Management**](/account-management/organization-management.md), select **Integrations**.
2. In the **Embase** panel, enter the Elsevier **API Key** and **Institutional Token**.
3. Select **Save**.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FWQcyk45z9DgCILUfgOU7%2Fintegrations.png?alt=media&amp;token=69cce72f-06d5-4803-ac66-8360f48031fa" alt="Embase integration panel with fields for an API Key and Institutional Token."><figcaption><p>Enter your Elsevier API Key and Institutional Token in the Embase integration panel.</p></figcaption></figure>

### Obtain Credentials

Elsevier issues an **API Key** and an **Institutional Token** to authenticate the integration.

{% stepper %}
{% step %}

#### Create An API Key

Create the **API Key** in the Elsevier Developer Portal.

1. Go to the [Elsevier Developer Portal](https://dev.elsevier.com/).
2. Select **I want an API Key**.
3. Sign in with your institutional email address. Create an Elsevier account if needed.
4. Select **Create API Key**, enter a label, and accept the API service agreement.
5. Copy the generated key and store it securely.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FXv3NzQiSEMoINccfnrzW%2FScreenshot-2026-07-03-at-14.22.25-2048x636.png?alt=media&amp;token=6e1e9f95-ea34-4f84-9344-16b49196ee7d" alt="Elsevier Developer Portal showing the I want an API Key option."><figcaption><p>Select <strong>I want an API Key</strong> in the Elsevier Developer Portal.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Request An Institutional Token

Elsevier's API support team issues the **Institutional Token** on request.

1. Email <apisupport@elsevier.com> from your institutional email address.
2. Include the **API Key** from the previous step.
3. State that you need remote API access for Nested Knowledge.

The token is tied to the API Key. Treat it as a password because it grants subscription-level access.

See the [Embase API guide](https://supportcontent.elsevier.com/Support%20Hub/DaaS/Embase%20API%20Guide.pdf) for more information. Then [connect Embase](#connect-embase).
{% endstep %}
{% endstepper %}

### Search Embase

Once your Embase integration has been set up, it is available for adding an [Automatic Search](/review-workflow/literature-search/add-search/automatic-search.md) into your nest.


---

# 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.nested-knowledge.com/integrations/embase-integration.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.