/openaire/research_products

POST /api/openaire/research_products

Price: 1 credit

Get an OpenAIRE research product (publication, dataset, software) by its id or DOI

How to use it

Get full details of a single research product by its OpenAIRE id or DOI. Returns the title and subtitle, abstract descriptions, authors with ranks, publication date and publisher, language, countries, subjects, the access rights and open-access colour, persistent identifiers, journal or container metadata, all access instances with their URLs and licences, citation-impact metrics (citation count, influence, popularity, impulse), and open-science flags.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — OpenAIRE research-product id, or a DOI / persistent identifier of the work (examples: "doi_________::b459128ec6a39036b85233a9d2468398", "10.18751/climate/scenarios/ch2025/brochure/1.0/en"; minLength: 1)

Response

• @type string (default: "OpenaireResearchProduct")
• id string required
• type string nullable
• main_title string nullable
• sub_title string nullable
• descriptions array (default: [])
• publication_date string nullable
• publisher string nullable
• language object nullable
  • @type string (default: "OpenaireLanguage")
  • code string nullable
  • label string nullable
• countries array (default: [])
  • @type string (default: "OpenaireCountry")
  • code string nullable
  • label string nullable
• authors array (default: [])
  • @type string (default: "OpenaireAuthor")
  • full_name string nullable
  • name string nullable
  • surname string nullable
  • rank integer nullable
  • pid object nullable
    • @type string (default: "OpenairePid")
    • scheme string nullable
    • value string nullable
• contributors array (default: [])
• subjects array (default: [])
• best_access_right object nullable
  • @type string (default: "OpenaireAccessRight")
  • code string nullable
  • label string nullable
  • scheme string nullable
• open_access_color string nullable
• pids array (default: [])
  • @type string (default: "OpenairePid")
  • scheme string nullable
  • value string nullable
• original_ids array (default: [])
• container object nullable
  • @type string (default: "OpenaireContainer")
  • name string nullable
  • issn_printed string nullable
  • issn_online string nullable
  • issn_linking string nullable
  • iss string nullable
  • vol string nullable
  • sp string nullable
  • ep string nullable
  • edition string nullable
  • conference_place string nullable
  • conference_date string nullable
• instances array (default: [])
  • @type string (default: "OpenaireInstance")
  • type string nullable
  • urls array (default: [])
  • doi string nullable
  • license string nullable
  • refereed string nullable
  • publication_date string nullable
• citation_count integer nullable
• influence number nullable
• popularity number nullable
• impulse number nullable
• is_green boolean nullable
• is_in_diamond_journal boolean nullable
• publicly_funded boolean nullable
• code_repository_url string nullable
• programming_language string nullable
• formats array (default: [])
• sources array (default: [])
• coverages array (default: [])
• date_of_collection string nullable
• embargo_end_date string nullable
• version string nullable
• size string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Research product not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.