POST /api/banpt/new_programmes/search
Price: 20 credits
Search BAN-PT's decisions on proposed new Indonesian study programmes against the minimum accreditation requirements, by institution, programme name, level, decision and the date the proposal was received. Each record carries the institution and programme names, level, date received, decision and decision date.
Use this to see which proposed Indonesian study programmes were cleared to open and when; names are in Indonesian as published.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results (min: 1)offset integer — Number of matching programmes to skip (default: 0; min: 0)institution string nullable — Words of the institution name, each matched anywhere in it, ignoring letter case (examples: "Universitas Negeri Makassar", "Institut Teknologi")keyword string nullable — Words of the programme name, each matched anywhere in it, ignoring letter case (examples: "Matematika", "data science")level string nullable — Programme level (one of: "diploma_1", "diploma_2", "diploma_3", "diploma_4", "bachelor", "applied_bachelor", "master", "applied_master", "doctorate", "applied_doctorate", "professional", "specialist", "subspecialist")decision string nullable — Decision on the proposal (one of: "meets_minimum", "does_not_meet_minimum", "returned_to_ministry", "returned_to_proposer", "validation")received_from integer nullable — Earliest date the proposal was received, unix seconds (examples: 1704067200; min: 0)received_to integer nullable — Latest date the proposal was received, unix seconds (examples: 1735603200; min: 0)@type string (default: "BanptNewProgramme")name string nullableinstitution string requiredlevel union nullablereceived_date integer nullabledecision union nullabledecided_date 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 — The entity was not found, or a precondition failed 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.