# /ruct/studies/search

`POST /api/ruct/studies/search`

Price: 1 credit

Search the officially recognised degrees in Spain's RUCT register by title, study code, university, academic level, regulation, branch, field of study, registration status and situation, optionally with every earlier registered version. Each study carries its id, code, title, university, academic level, status, situation and the id of its latest registered application

## How to use it

With no filter it lists the studies in the register, extinct ones included. Pass a returned id to ruct/studies for credits, dates, authorisations, centres and history. Titles and values are in Spanish.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, nullable) — Text contained in the study title (examples: "Medicina"; minLength: 1)
- `code` (string, nullable) — 7-digit RUCT study code (examples: "2504266")
- `university` (string, nullable) — 3-digit RUCT university code (examples: "022")
- `study_type` (string, nullable) — Academic level of the study (one of: "Grado", "Máster", "Doctor", "Ciclo", "Título Equivalente", "Título Extranjero"; examples: "Máster")
- `subtype` (string, nullable) — Regulation or cycle the study falls under (one of: "Grado - RD 1393/2007", "Grado - RD 822/2021", "Máster - RD 1393/2007", "Máster - RD 56/2005", "Máster - RD 822/2021", "Doctor - RD 99/2011", "Doctor - RD 56/2005", "Doctor - RD 1393/2007", "Ciclo Corto", "Ciclo Largo", "Primer Ciclo de Ciclo Largo", "Segundo Ciclo de Ciclo Largo", "Sólo Segundo Ciclo", "Título Equivalente", "Título Extranjero"; examples: "Grado - RD 822/2021")
- `branch` (string, nullable) — Branch of knowledge (one of: "Artes y Humanidades", "Ciencias", "Ciencias de la Salud", "Ciencias Sociales y Jurídicas", "Ingeniería y Arquitectura"; examples: "Ciencias de la Salud")
- `field_of_study` (string, nullable) — Field of study (one of: "Actividad física y ciencias del deporte", "Arquitectura, construcción, edificación y urbanismo, e ingeniería civil", "Biología y genética", "Bioquímica y biotecnología", "Ciencias agrarias y tecnología de los alimentos", "Ciencias Biomédicas", "Ciencias de la educación", "Ciencias de la Tierra", "Ciencias del comportamiento y psicología", "Ciencias económicas, administración y dirección de empresas, márquetin, comercio, contabilidad y turismo", "Ciencias medioambientales y ecología", "Ciencias sociales, trabajo social, relaciones laborales y recursos humanos, sociología, ciencia política y relaciones internacionales", "Derecho y especialidades jurídicas", "Enfermería", "Estudios de género y estudios feministas", "Farmacia", "Filología, estudios clásicos, traducción y lingüística", "Física y astronomía", "Fisioterapia, podología, nutrición y dietética, terapia ocupacional, óptica y optometría y logopedia", "Historia, arqueología, geografía, filosofía y humanidades", "Historia del arte y de la expresión artística, y bellas artes", "Industrias Culturales: diseño, animación, cinematografía y producción audiovisual", "Ingeniería eléctrica, ingeniería electrónica e ingeniería de la telecomunicación", "Ingeniería industrial, ingeniería mecánica, ingeniería automática, ingeniería de la organización industrial e ingeniería de la navegación", "Ingeniería informática y de sistemas", "Ingeniería química, ingeniería de los materiales e ingeniería del medio natural", "Interdisciplinar", "Matemáticas y estadística", "Medicina y Odontología", "Periodismo, comunicación, publicidad y relaciones públicas", "Química", "Veterinaria"; examples: "Ingeniería informática y de sistemas")
- `status` (string, nullable) — Registration status (one of: "Publicado en B.O.E.", "Autorizado por Comunidad Autónoma", "Afectado por Resolución Judicial"; examples: "Publicado en B.O.E.")
- `situation` (string, nullable) — Whether the study is active, extinct or being extinguished (one of: "Alta", "Extinguida", "A extinguir"; examples: "Alta")
- `include_history` (boolean) — Also return one row per earlier registered version of each study (default: false; examples: true)
- `count` (integer, required) — Max number of studies to return (min: 1; max: 250)

## Response

### 200 — Successful Response

- `@type` (string) (default: "RuctStudyListing")
- `id` (string, required)
- `code` (string, required)
- `cycle_code` (string, required)
- `type_code` (string, required)
- `name` (string, nullable)
- `university` (string, nullable)
- `level` (string, nullable)
- `status` (string, nullable)
- `situation` (string, nullable)
- `application_id` (string, nullable)
- `url` (string, required)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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 study in the register matches these filters

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.

