/repec/institutions

POST /api/repec/institutions

Price: 1 credit

Get one economics institution from the EDIRC directory by its code: name, location, homepage, phone, postal address, subject areas, sub-departments, the series it publishes and the RePEc authors who list it as their workplace

How to use it

This is the way from an institution to its people and its output: every `members[].short_id` resolves through /repec/authors, and every `published_series` is a series whose records /repec/series lists. A record from /repec/papers reaches its publisher's entry here through the EDIRC code, and an author profile carries `institution_id` for the same purpose. `members` covers only authors registered with the RePEc Author Service who claimed this affiliation themselves, so it is a subset of the staff, not a roster. The directory left `email` empty on every entry sampled while building this endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — EDIRC institution code, its `RePEc:edi:` handle, or an EDIRC institution URL (examples: "frbclus", "RePEc:edi:decituk", "https://edirc.repec.org/data/nberrus.html"; minLength: 1)

Response

• @type string (default: "RepecInstitution")
• id string required
• url string required
• name string required
• location string nullable
• region string nullable
• homepage_url string nullable
• email string nullable
• phone string nullable
• fax string nullable
• postal_address string nullable
• areas array (default: [])
• parent_id string nullable
• subentities array (default: [])
  • @type string (default: "RepecInstitutionRef")
  • id string required
  • name string required
  • url string required
  • location string nullable
  • region string nullable
• published_series array (default: [])
  • @type string (default: "RepecInstitutionSeries")
  • series_title string required
  • url string required
  • series_id string nullable
• members array (default: [])
  • @type string (default: "RepecInstitutionMember")
  • name string required
  • short_id string nullable
  • profile_url string nullable
• member_count integer nullable
• alumni array (default: [])
  • @type string (default: "RepecInstitutionMember")
  • name string required
  • short_id string nullable
  • profile_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 EDIRC institution with this code 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.