/repec/papers

POST /api/repec/papers

Price: 1 credit

Get one RePEc item by its handle: title, authors, abstract, keywords, JEL codes, date, series and publisher, journal volume and pages, DOI, citation count, download links and other versions of the same work

How to use it

One handle resolves every kind of RePEc record through the same call — working paper, journal article, book chapter and software component — so the type need not be known first; read `item_type` to tell them apart and `series_id` to list the rest of the same series through /repec/series. `abstract`, `jel_codes` and `keywords` come from the archive that deposited the record, so older records and software components often carry none of them: read an empty one as unrecorded, not as an absent topic. `related_works` links the other versions of the same work, which is how a working paper and its published article are connected.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — RePEc handle of the item, or its EconPapers URL (examples: "RePEc:nbr:nberwo:33000", "RePEc:eee:reveco:v:64:y:2019:i:c:p:217-241", "https://econpapers.repec.org/paper/nbrnberwo/33000.htm"; minLength: 1)

Response

• @type string (default: "RepecPaper")
• id string required
• url string required
• record_title string required
• item_type string nullable
• authors array (default: [])
  • @type string (default: "RepecAuthorRef")
  • name string required
  • short_id string nullable
  • profile_url string nullable
• abstract string nullable
• keywords array (default: [])
• jel_codes array (default: [])
• published_date string nullable
• year integer nullable
• series_name string nullable
• series_id string nullable
• series_url string nullable
• publisher_name string nullable
• publisher_url string nullable
• number string nullable
• volume string nullable
• issue string nullable
• pages string nullable
• page_count integer nullable
• doi string nullable
• isbn string nullable
• language string nullable
• requires string nullable
• note string nullable
• nep_reports array (default: [])
• editors array (default: [])
• citation_count integer nullable
• downloads array (default: [])
  • @type string (default: "RepecDownload")
  • url string required
  • content_type string nullable
  • note string nullable
• related_works array (default: [])
  • @type string (default: "RepecRelatedWork")
  • id string nullable
  • record_title string required
  • url string required
  • kind string nullable
  • relation string nullable
  • source_name string nullable
  • year integer nullable
  • citation_count integer nullable
• chapters array (default: [])
  • @type string (default: "RepecRelatedWork")
  • id string nullable
  • record_title string required
  • url string required
  • kind string nullable
  • relation string nullable
  • source_name string nullable
  • year integer nullable
  • citation_count integer nullable
• ordering_url string nullable
• access_statistics_url 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 — No RePEc item with this handle 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.