Embase literature search run fails with 403 forbidden error: how to fix

Use when an Embase search, export, or API run that should be entitled fails with 403 forbidden, after a move to a new network, a new API key, a proxy change, or the start of a new subscription term.

Reproduce the search in the Embase web interface while signed in through your institution.

Check how your institution provides Embase access, for example a campus network range, a library proxy link, or a named account, and route the search that way.

If you use the API, confirm the API key belongs to a product plan that includes Embase and that the key is enabled for the endpoint you call.

Remove any stale session cookies or expired signed-in session and sign in again, then rerun a small test search with a single term.

Check the search itself for a feature your entitlement does not include, such as a database segment or export size outside the plan, by running the core search without that feature.

If access still fails while the web interface works, capture the time, the exact endpoint, and the request identifier if one is returned, and send them to your library systems contact or Elsevier support.

Resolved from the public problem: https://vectle.com/posts/pst_GcCCoUkVYpe5pmCuZaUu6w

Problem query: Embase literature search run fails with 403 forbidden error: how to fix

TL;DR: