POST /api/eqe/accreditations
Price: 5 credits
Get one record of the NCEQE register of authorisation and accreditation decisions on Georgian higher education institutions and programmes by its URL or id: activity, institution, decision, condition, validity dates, decision date and number, report, decision and minutes documents, and on programme records the programme and qualification names, cycle and NQF level, study level, language, ISCED-F field, ECTS credits and place of delivery.
Read one Georgian accreditation or authorisation decision record. Find record ids with eqe/accreditations/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)accreditation string required — NCEQE register record URL or id (examples: "https://eqe.ge/en/deqars/1631/show", "1631")language string — Language of the record text (default: "en"; one of: "en", "ka")@type string (default: "EqeAccreditation")id string nullableurl string nullablelanguage string nullableactivity string nullableactivity_code string nullable (one of: "institution_authorisation", "programme_accreditation", "accreditation_monitoring", "authorisation_monitoring", "programme_addition", "student_quota_increase", "authorisation_follow_up_report", "accreditation_follow_up_report", "decision_amendment", "joint_programme_accreditation")institution_name string nullableinstitution_names array (default: [])programme_name string nullablequalification_name string nullablequalification_level string nullableehea_cycle string nullablenqf_level integer nullablestudy_level string nullableprogramme_language string nullableisced_code string nullableisced_field string nullableects integer nullableimplementation_place string nullableis_joint_programme boolean nullabledecision string nullablecondition string nullablecondition_term string nullablemax_student_count_before integer nullablemax_student_count_after integer nullablecouncil string nullableamendment_title string nullablevalid_from_date integer nullablevalid_to_date integer nullabledecision_date integer nullabledecision_number string nullablereport_urls array (default: [])decision_document_urls array (default: [])minutes_urls array (default: [])other_attributes array (default: [])@type string (default: "EqeAttribute")label string nullablevalue string 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 register record exists at that id. 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.