Download website data in JSON data format

JSON (JavaScript Object Notation) files are text-based, machine-readable data files with structured patterns.

Publishing data in this format allows EMA to provide users using automated systems with a source of information for the data and documents that is easy and efficient to extract. The files can be used by anyone who is programmatically fetching documents or metadata.

The website automatically updates these JSON data files twice a day, at 06:00 and 18:00 Amsterdam time (Central European Time, CET). The date and time of the JSON file update are included at the start of each JSON data file.

For medicines and related procedures, data is also available in a table format via the link below. The data in the JSON files and the data tables are the same:

Download medicines data tables

Rollout

EMA’s entire website is available in JSON format. Content types were added in stages, with full coverage completed on 20 January 2026

The JSON data files are available via the links on this page. You can also see what data is included within the files by opening the expandable sections below the links.

Rollout timeline

20 January 2026: Events and meetings

News

Guidance and information covering remaining website sections
Mid-November 2025: All documents published on this website, including medicine-related content, product information, translations, and guidelines. All medicine and medicine-related procedures pages.

Documents

You can download JSON data for all documents published on the EMA website using the links below. The files include, for example, product information, guidelines, and other regulatory and procedural documents.

To make these files manageable, the data is split into three separate files:

All documents in English JSON data file: Includes all documents published on the EMA website in English. Data of these English language documents are also included in the two JSON data files below, where these documents are grouped with their translations where available.
Documents related to centrally authorised medicines and translations JSON data file: Includes documents related to centrally authorised medicines, grouped with their translations where available
Other documents and translations JSON data file: Includes all remaining documents and translations that are not related to centrally authorised medicines

Click on the expandable sections below to see what data is included within the files.

For documents in this file, the data and their keys include:

document name: “name”
document type: “type”
status and consultation date (for documents that are or have been open for consultations): “status”; “consultation_date”
first published date: “first_published_date”
last updated date: “last_updated_date”
document reference number: “reference_number”
document URL: “document_url”

For documents related to centrally authorised medicines and their translations (if available), the data and their keys include:

document name: “name”
document type: “type”
first published date: "first_published_date”
last updated date: “last_updated_date”
document reference number: “reference_number”
document URL: “document_url”
translations with ISO language code and corresponding URL: “translations”, ISO language code for example “bg” and its URL

The default keys “status” and “consultation_date” are included, although no associated values are present in the data file.

For documents not related to centrally authorised medicines and their translations (where available), the data and their keys include:

document name: “name”
document type: “type”
status and consultation date (for documents that are or have been open for consultations): “status”; “consultation_date”
first published date: “first_published_date”
last updated date: “last_updated_date”
document reference number: “reference_number”
document URL: "document_url”
translations with ISO language code and corresponding URL: “translations”, ISO language code for example “bg” and its URL

Guidance and information

Guidance and information JSON data file: Includes general pages published on the EMA website covering website sections not covered by other JSON data files. For example EMA’s guidance, scientific guidelines, and other information.

For guidance and information pages in this file, the data and their keys include:

page title: “title”
page summary: “summary”
content category (values: human, veterinary, herbal, corporate): “categories”
first published date: “first_published_date”
last updated date: “last_updated_date”
page URL: “general_url”

Medicines and post-authorisation procedures for medicines

Medicine pages JSON data file: Includes medicines for which a marketing authorisation application has been submitted through the centralised procedure with EMA. Information on medicines under evaluation is published monthly in separate lists on Medicines for human use under evaluation
Post-authorisation procedures for medicines JSON data file: Includes medicines for which marketing authorisation holders have submitted an application to change the terms of marketing authorisation, also known as variations. Information on approved post-authorisation procedures is available on individual medicine pages.

Click on the expandable section below to see what data is included within the files.

For veterinary medicines, the data provided is limited to key data. Full, up-to-date information can be found on the Veterinary Medicines Information website.

For medicines in this file, the data and their keys include:

category (human or veterinary): “category”
name of medicine: “name_of_medicine”
EMA product number: “ema_product_number”
medicine status in the centralised procedure: “medicine_status”
opinion status: “opinion_status”
Latest procedure affecting product information (if applicable): “latest_procedure_affecting_product_information”
International non-proprietary name (INN) / common name: “international_non_proprietary_name_common_name”
active substance: “active_substance”
therapeutic area (MeSH) (human medicines): “therapeutic_area_mesh”
species (veterinary): "species_veterinary"
patient safety: "patient_safety"
ATC code (human): "atc_code_human"
ATCvet code (veterinary): "atcvet_code_veterinary"
pharmacotherapeutic group (human or veterinary): “pharmacotherapeutic_group_human” or pharmacotherapeutic_group_veterinary”
therapeutic indication: "therapeutic_indication"
medicine types (for example advanced therapy, biosimilar, exceptional circumstances, generic or hybrid, orphan, PRIME: priority medicines): “advanced_therapy: Yes”,
marketing authorisation developer, applicant or holder: "marketing_authorisation_developer_applicant_holder"
European Commission decision date: "european_commission_decision_date"
dates related to procedural steps: for example "opinion_adopted_date"
revision number: "revision_number"
first published date: "first_published_date"
last updated date: "last_updated_date"
medicine page URL: "medicine_url"

For post-authorisation procedures data included are opinions and withdrawn applications. Information on approved post-authorisation procedures is available on individual medicine pages.

For post-authorisation procedures for medicines in this file, the data and their keys include:

category (human or veterinary): “category”
name of medicine: “name_of_medicine”
EMA product number: “ema_product_number”
active substance: “active_substance”
International non-proprietary name (INN) / common name: “international_non_proprietary_name_common_name”
therapeutic area (MeSH): “therapeutic_area_mesh”
ATC code (human): "atc_code_human"
ATCvet code (veterinary): "atcvet_code_veterinary"
species (veterinary): "species_veterinary"
medicine types (for example additional monitoring, advanced therapy, biosimilar, generic or hybrid, orphan, PRIME: priority medicines): for example “advanced_therapy: Yes”,
marketing authorisation developer, applicant or holder: "marketing_authorisation_developer_applicant_holder"
status in the centralised post-authorisation procedure: "post_authorisation_procedure_status", followed by status, for example “Opinion” and “post-authorisation_opinion_status”: “Positive”
dates related to procedural steps: for example "post-authorisation_opinion_date"
first published date: "first_published_date"
last updated date: "last_updated_date"
medicine page URL: "medicine_url"