Overview

V3 is the latest and recommended version of the OpenAIRE Graph API, superseding V1 and V2. It keeps the familiar parameter-based query style — one query parameter per filter — so most existing V1/V2 calls translate with only minor changes, while adding a substantially larger set of filters, new entity fields, and consistent endpoint paths and value formats across all entities.

If you are starting fresh, jump to the Quickstart. If you are coming from V1/V2, the rest of this page summarizes everything that changed.

Endpoint paths

All entities are now served under a single, consistently named /v3 path (lowercase, hyphenated). Notably, Persons is promoted from a V1-only endpoint to a first-class V3 endpoint.

Entity	V1/V2 endpoint	V3 endpoint
Research products	GET /v2/researchProducts	GET /v3/research-products
Organizations	GET /v1/organizations	GET /v3/organizations
Data sources	GET /v1/dataSources	GET /v3/datasources
Projects	GET /v1/projects	GET /v3/projects
Persons	GET /v1/persons	GET /v3/persons

The query conventions are unchanged: filters combine with AND by default, repeated parameters (or comma-separated values) combine with OR, and most text/identifier fields accept inline AND / OR / NOT expressions. The top-level logicalOperator (default AND) still controls how different fields combine.

Renamed parameters (research products)

A few filters were renamed and their accepted values made more readable:

V1/V2	V3	What changed
authorOrcid	authorId	Generalized to any author identifier (ORCIDs still work).
bestOpenAccessRightLabel	accessRightLabel	Values are now human-readable: Open Access, Closed Access, Restricted, Open Source, Embargo, Unknown (previously OPEN, CLOSED, EMBARGO, …).
sdg	sdgLabel	Now a label such as 13. Climate action instead of an integer 1–17. See the list of values.

New filters

Research products

New filters added in V3 (full reference):

• Year-based dates — fromPublicationYear, toPublicationYear, publicationYear, and excludePubDateRange (negate a publication-date range), complementing the existing fromPublicationDate / toPublicationDate.
• Content — language, hasLicense, eoscIfGuidelines.
• Funding hierarchy — relFunder, relFundingLevel0Id, relFundingLevel1Id, relFundingLevel2Id.
• Relations by name (not just id) — relOrganization, relProject, relHostingDataSource, relCommunityName.
• Communities — subCommunity.
• Data source — source (match products collected from or hosted by a data source).

Data sources

New filters in V3 (full reference):

• collectedFromName, country, thematic, jurisdiction, eoscdatasourcetype, odLanguages, compatibilityId, compatibilityName.

Projects

New filters in V3 (full reference):

• Year-based dates — fromStartYear, toStartYear, fromEndYear, toEndYear, startYear, endYear, activeYear (in addition to the existing date-based fromStartDate / toStartDate / fromEndDate / toEndDate).
• Funding — funder, fundinglevel0Id, fundinglevel1Id, fundinglevel2Id.
• Other — country, projectOAMandatePublications.

Organizations & Persons

The set of filters is unchanged from V1; only the endpoint path moved to /v3 (organizations, persons).

Cross-cutting themes

• Consistent versioning — every entity (including Persons) is now under /v3 with uniform path naming.
• Filter by year, not only by full date, for research products and projects.
• Funding-stream hierarchy filters (levels 0–2) for research products and projects.
• Filter by related-entity name in addition to id (organizations, projects, data sources, communities, funders).
• Readable value formats for access rights and SDGs.