/core/outputs

POST /api/core/outputs

Price: 1 credit

Get a CORE output (a work's deposit in a repository) by ID or URL

How to use it

Get a CORE output by ID or URL. An output is a specific deposit of a research work in a single repository (a work can have multiple outputs from different sources). Returns title, abstract, authors, identifiers, the source repository (data provider), download URL, full-text URLs, subjects, tags, license, cited references (bibliography), and date metadata.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• output string required — CORE output ID or output URL (examples: "641684400", "https://core.ac.uk/outputs/641684400"; minLength: 1)

Response

• @type string (default: "CoreOutput")
• id integer required
• url string required
• abstract string nullable
• full_text string nullable
• authors array (default: [])
  • @type string (default: "CoreAuthor")
  • name string required
• contributors array (default: [])
• orcids array (default: [])
• doi string nullable
• document_type string nullable
• year_published integer nullable
• language string nullable
• publisher string nullable
• license string nullable
• fulltext_status string nullable
• download_url string nullable
• source_fulltext_urls array (default: [])
• urls array (default: [])
  • @type string (default: "CoreWorkLink")
  • type string nullable
  • url string nullable
• subjects array (default: [])
• tags array (default: [])
• identifiers array (default: [])
  • @type string (default: "CoreIdentifier")
  • type string nullable
  • identifier string nullable
• data_provider object nullable
  • @type string (default: "CoreWorkDataProvider")
  • id integer nullable
  • name string nullable
  • url string nullable
  • image string nullable
• links array (default: [])
  • @type string (default: "CoreWorkLink")
  • type string nullable
  • url string nullable
• references array (default: [])
  • @type string (default: "CoreWorkReference")
  • id string nullable
  • authors array (default: [])
  • date string nullable
  • doi string nullable
  • raw string nullable
• created_at string nullable
• updated_at string nullable
• accepted_at string nullable
• deposited_at string nullable
• published_at 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 — Output 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.