/repec/authors

POST /api/repec/authors

Price: 20 credits

Get one registered RePEc author by short-id: name, homepage, phone, postal address, workplace and its EDIRC institution, and the full bibliography grouped by kind of work, each entry with its handle, title, year, series and citation count

How to use it

This endpoint takes a short-id, not a name, and no endpoint here turns a name into one: read it from the `authors[].short_id` of a record returned by /repec/papers, or from the members list of an institution from /repec/institutions. Only authors who registered with the RePEc Author Service have a profile at all, and roughly half the names on a record do not carry a short_id. The bibliography covers the whole career in one response and is grouped by kind of work, so `work_groups` is the place to read publication counts rather than counting search results.

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 Author Service short-id, or an EconPapers author profile URL (examples: "pbe23", "psi78", "https://econpapers.repec.org/RAS/pbe23.htm"; minLength: 1)

Response

• @type string (default: "RepecAuthor")
• id string required
• url string required
• name string required
• email string nullable
• homepage_url string nullable
• phone string nullable
• fax string nullable
• postal_address string nullable
• workplace_name string nullable
• workplace_url string nullable
• institution_id string nullable
• institution_url string nullable
• last_updated_date string nullable
• access_statistics_url string nullable
• work_count integer nullable
• work_groups array (default: [])
  • @type string (default: "RepecAuthorWorkGroup")
  • section string required
  • works array (default: [])
    • @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: [])

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 registered RePEc author with this short-id 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.