/nber/papers

POST /api/nber/papers

Price: 5 credits

Get one NBER paper by its number: title, authors, DOI, issue date, abstract, topics, programs, acknowledgements, the formatted citation, published journal versions, associated links and news coverage

How to use it

The series letter is part of the number and cannot be dropped: w is the working paper series, t technical working papers and h historical, and a bare number resolves to nothing. NBER records no JEL codes at all, so use `topics` and `programs` for subject classification, and follow `programs[].alias` into /nber/programs. On pre-1980 papers `programs` is usually there while `topics` is rare, and an empty list means unclassified rather than off-topic. `published_versions` names the journal the paper finally appeared in, when it did.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — NBER paper number, including its series letter, or the paper's URL (examples: "w5161", "t0001", "https://www.nber.org/papers/w32379"; minLength: 1)

Response

• @type string (default: "NberPaper")
• id string required
• url string required
• record_title string required
• doi string nullable
• authors array (default: [])
  • @type string (default: "NberPersonRef")
  • name string required
  • alias string nullable
  • profile_url string nullable
• published_date string nullable
• issue_date string nullable
• paper_series_label string nullable
• institution string nullable
• pdf_url string nullable
• abstract string nullable
• topics array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• programs array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• working_groups array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• conferences array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• acknowledgements string nullable
• citation string nullable
• published_versions array (default: [])
• revisions array (default: [])
  • @type string (default: "NberLink")
  • link_title string required
  • url string required
  • source string nullable
  • published_at string nullable
• associated_links array (default: [])
  • @type string (default: "NberLink")
  • link_title string required
  • url string required
  • source string nullable
  • published_at string nullable
• news_mentions array (default: [])
  • @type string (default: "NberLink")
  • link_title string required
  • url string required
  • source 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 — No NBER paper with this number 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.