POST /api/ipeds/institutions/admissions
Price: 1 credit
Get the IPEDS admissions record of one US college or university for a survey year — applications, admissions and first-time enrolment split by sex, the SAT and ACT score percentiles of enrolled students, and how the institution weighs each admission requirement
Admissions selectivity and entry test scores for one UNITID. Every requirement is reported as how the institution treats it — required, recommended, considered, or neither — rather than as a yes/no, so read the value rather than testing for presence. The percentiles describe students who enrolled and submitted that test, not applicants, and `sat_submitted_percent` says how few that can be; an institution that reports no scores at all is usually open-admission, which `has_open_admissions_policy` states directly. `by_sex` carries one row per sex plus a total row, so sum nothing yourself. Two surveys back this endpoint and they end in different years: requirements and test scores stop after 2022, application counts continue, so a later year returns `by_sex` alone.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)institution string required — IPEDS UNITID of the institution (examples: "166683", "104151", "166027"; minLength: 1)year integer — Survey year the admissions record is read for (default: 2022; min: 1990; max: 2100)@type string (default: "IpedsAdmissions")id string requiredinstitution_id string requiredyear integer nullablehas_open_admissions_policy boolean nullableadmits_no_entering_freshmen boolean nullableyears_of_college_required integer nullablerequirements object nullable@type string (default: "IpedsAdmissionRequirements")high_school_record string nullablehigh_school_gpa string nullablehigh_school_rank string nullablehigh_school_diploma_or_equivalent string nullablecollege_preparatory_programme string nullabledemonstrated_competencies string nullablerecommendations string nullablepersonal_statement string nullableadmission_test_scores string nullablesat_scores string nullableother_test_scores string nullabletoefl string nullableability_to_benefit_test string nullablelegacy_status string nullablework_experience string nullablestate_residence string nullableminimum_age string nullableother string nullabletest_scores object nullable@type string (default: "IpedsTestScores")sat_submitted_count integer nullablesat_submitted_percent number nullablesat_reading_25th integer nullablesat_reading_50th integer nullablesat_reading_75th integer nullablesat_math_25th integer nullablesat_math_50th integer nullablesat_math_75th integer nullablesat_writing_25th integer nullablesat_writing_75th integer nullableact_submitted_count integer nullableact_submitted_percent number nullableact_composite_25th integer nullableact_composite_50th integer nullableact_composite_75th integer nullableact_english_25th integer nullableact_english_50th integer nullableact_english_75th integer nullableact_math_25th integer nullableact_math_50th integer nullableact_math_75th integer nullableact_writing_25th integer nullableact_writing_75th integer nullablereporting_period string nullableby_sex array (default: [])@type string (default: "IpedsAdmissionsBySex")sex string nullableapplied_count integer nullableadmitted_count integer nullableenrolled_count integer nullableenrolled_full_time_count integer nullableenrolled_part_time_count integer 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 IPEDS admissions record for that UNITID in that survey year 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.