/ipeds/institutions/costs

POST /api/ipeds/institutions/costs

Price: 1 credit

Get the published price of attending one US college or university in an academic year — tuition and required fees by level of study and residency, the part-time credit-hour charge, and room, board, books and other expenses by living arrangement

How to use it

Sticker price for one UNITID, not what students actually pay: these are the published charges before any grant or scholarship. `residency` is what separates the tuition lines at a public institution — in-district, in-state and out-of-state are different rows for the same level of study — so pick the line that matches the student rather than the first one. `tuition_full_time` and `tuition_published` are two different reporting bases and an institution may fill only one. `year` is the starting year of the academic year. Private institutions report a single tuition line, and institutions that charge per programme rather than per year report tuition here as absent.

Parameters

• access-token string required

Request body

• timeout 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 — Academic year the published prices are read for (default: 2023; min: 1986; max: 2100)

Response

• @type string (default: "IpedsCosts")
• id string required
• institution_id string required
• year integer nullable
• tuition array (default: [])
  • @type string (default: "IpedsTuitionLine")
  • level_of_study string nullable
  • residency string nullable
  • tuition_full_time integer nullable
  • fees_full_time integer nullable
  • tuition_and_fees_full_time integer nullable
  • tuition_published integer nullable
  • fees_published integer nullable
  • tuition_and_fees_published integer nullable
  • tuition_published_change_percent number nullable
  • fees_published_change_percent number nullable
  • part_time_credit_hour_charge integer nullable
• living_costs array (default: [])
  • @type string (default: "IpedsLivingCostLine")
  • level_of_study string nullable
  • living_arrangement string nullable
  • room_and_board integer nullable
  • books_and_supplies integer nullable
  • other_expenses integer 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 IPEDS price record for that UNITID in that academic 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.

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.