POST /api/ruct/centers
Price: 1 credit
Get one centre of a Spanish university from the RUCT register: name, university, centre type, legal status, own or attached link, address, website, e-mail, phones, fax and its founding document with bulletin, provision type and dates
Pass an id from ruct/centers/search or from the centers of a ruct/studies record. A centre code can belong to several universities, so the id carries both. Values are in Spanish.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)center string required — RUCT centre id (university code/centre code), or its page URL in the register (examples: "053/28051852", "https://www.educacion.gob.es/ruct/centro.action?codigoUniversidad=053&codigoCentro=28051852"; minLength: 1)@type string (default: "RuctCenter")id string requiredcenter_code string requiredname string nullableuniversity_id string requireduniversity string nullablecenter_type string nullablelegal_status string nullablelink_type string nullableaddress string nullablepostal_code string nullablelocality string nullablemunicipality string nullableprovince string nullableregion string nullablewebsite string nullableemail string nullablephone string nullablephone_2 string nullablefax string nullablefounding_bulletin string nullablefounding_publication_year integer nullablefounding_provision_type string nullablefounding_provision_date integer nullablefounding_publication_date integer nullablefounding_effective_date integer nullableinstitutional_accreditation_date integer nullableinstitutional_accreditation_url string nullableurl string required422 — 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 centre with this university and centre code is in the register 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.