POST /api/mifuturo/programs
Price: 1 credit
Get a Mi Futuro study programme by its programme code
Get the full detail of one Chilean study programme by its programme code, including its fees, duration, vacancies, enrolment and admission weighting. Codes come from the search and institutions/programs endpoints.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)program string required — Mi Futuro programme code, from search or institutions/programs results. (examples: "I1S1C242J1V2", "I86S3C1J1V1")@type string (default: "MifuturoProgram")id string requiredname string requiredgeneric_career_id string nullablegeneric_career_name string nullableinstitution_id string nullableinstitution_name string nullableinstitution_type string nullablearea_id string nullablearea_name string nullableregion_id string nullableregion_name string nullableis_technical boolean nullableprogram_type string nullablecampus string nullableschedule string nullableannual_fee number nullablefee_currency string nullablegraduation_cost number nullableformal_duration_semesters integer nullablevacancies_first_semester integer nullableaccreditation string nullablenem_average number nullablepsu_average_first_year number nullablepsu_coverage_first_year string nullableentrants_municipal_share number nullableentrants_subsidized_private_share number nullableentrants_paid_private_share number nullableentrants_delegated_admission_share number nullableenrollment object nullable@type string (default: "MifuturoEnrollment")total integer nullablefemale integer nullablemale integer nullablefirst_year_total integer nullablefirst_year_female integer nullablefirst_year_male integer nullablegraduates integer nullablegraduates_female integer nullablegraduates_male integer nullableadmission_weights object nullable@type string (default: "MifuturoAdmissionWeights")grades number nullableranking number nullablelanguage number nullablemath number nullablemath_2 number nullablehistory number nullablescience number nullableother number nullable422 — 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 programme 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.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.