/repec/series

POST /api/repec/series

Price: 5 credits

List the records published in one RePEc series or journal. Returns each record's handle, its number within the series, title and authors

How to use it

Use this to walk a working-paper series or a journal end to end — NBER Working Papers, IMF Working Papers, a specific journal — once its `series_id` is known from a record returned by /repec/papers or /repec/papers/search. A row carries only the handle, number, title and authors; pass the handle to /repec/papers for the abstract, date, JEL codes and downloads. Ordering follows the series' own listing: descending number for a working paper series, which puts the newest first, but alphabetical by title for a chapter series.

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 series identifier, as the `series_id` of a record or the `RePEc:archive:series` form, or an EconPapers series URL (examples: "nbrnberwo", "RePEc:eee:reveco", "https://econpapers.repec.org/paper/nbrnberwo/"; minLength: 1)
• count integer required — Max number of records to return (examples: 100; min: 1; max: 5000)

Response

• @type string (default: "RepecItemCard")
• id string nullable
• url string required
• record_title string required
• item_type string nullable
• authors array (default: [])
• source_name string nullable
• series_id string nullable
• number string nullable
• year integer nullable
• keywords array (default: [])
• jel_codes array (default: [])
• created_date string nullable
• modified_date string nullable
• citation_count integer nullable
• has_downloads boolean 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

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 series with this identifier 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.