/nber/scholars/papers

POST /api/nber/scholars/papers

Price: 5 credits

List everything one NBER scholar produced — working papers, books, chapters, articles, datasets, lectures and interviews. Returns each record's node id, URL, title, co-authors, display date and abstract

How to use it

This is keyed on the scholar's own NBER identity rather than on their name, so it does not pick up records by another person with a similar name and it does not include the scholar's own profile page as a result. It covers NBER output only: a paper the scholar published elsewhere is absent, and /repec/authors reached through the `repec_url` on /nber/scholars is where a full bibliography comes from. Read `content_type` to separate the working papers from books, chapters and lectures.

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 scholar page slug, or the scholar's NBER profile URL (examples: "stephen_cecchetti", "https://www.nber.org/people/michael_bordo"; minLength: 1)
• count integer required — Max number of records to return (examples: 100; min: 1; max: 2000)

Response

• @type string (default: "NberSearchResult")
• id string required
• url string required
• alias string nullable
• record_title string required
• content_type string required
• content_type_name string nullable
• display_date string nullable
• authors array (default: [])
  • @type string (default: "NberPersonRef")
  • name string required
  • alias string nullable
  • profile_url string nullable
• editors array (default: [])
  • @type string (default: "NberPersonRef")
  • name string required
  • alias string nullable
  • profile_url string nullable
• presenters array (default: [])
  • @type string (default: "NberPersonRef")
  • name string required
  • alias string nullable
  • profile_url string nullable
• abstract string nullable
• quote string nullable
• image string nullable
• publication_type_name string nullable
• issue_print_url string nullable
• conference_type_name string nullable
• producer_label string nullable
• job_title string nullable
• university_affiliation string nullable
• back_office_id string nullable
• source_title string nullable
• source_url string nullable
• summer_institute_title string nullable
• summer_institute_url string nullable
• video_image string nullable
• video_type_name string nullable
• programs array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• projects array (default: [])
  • @type string (default: "NberTermRef")
  • name string required
  • alias string nullable
  • url string nullable
• related_papers array (default: [])
  • @type string (default: "NberPaperRef")
  • id string required
  • alias string nullable
  • url string nullable
• is_conference_announced boolean nullable
• is_certified_random boolean nullable
• is_new_this_week boolean 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 scholar page with this slug 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.