POST /api/aishe/directory/search
Price: 100 credits
Search the AISHE institution directory — universities, colleges or standalone institutions — by state, district, institution type and affiliating university. Each record carries its AISHE code, name, state, district, address, website, management, year of establishment, institution type, rural/urban location and, for colleges, the affiliating university.
Use this for the richest AISHE institution record — website, year of establishment, management and affiliating university; pick the directory with `category`. For the full registry including closed institutions and R&D bodies use aishe/institutions/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category string required — Directory to search: university, college or standalone institution (one of: "university", "college", "standalone")count integer required — Max number of results (min: 1; max: 55000)name string nullable — Part of the institution name (examples: "Indian Institute", "Parul University")state string nullable — Indian state or union territory of the institution (one of: "Andaman and Nicobar Islands", "Andhra Pradesh", "Arunachal Pradesh", "Assam", "Bihar", "Chandigarh", "Chhattisgarh", "Delhi", "Goa", "Gujarat", "Haryana", "Himachal Pradesh", "Jammu and Kashmir", "Jharkhand", "Karnataka", "Kerala", "Ladakh", "Lakshadweep", "Madhya Pradesh", "Maharashtra", "Manipur", "Meghalaya", "Mizoram", "Nagaland", "Odisha", "Puducherry", "Punjab", "Rajasthan", "Sikkim", "Tamil Nadu", "Telangana", "The Dadra and Nagar Haveli and Daman and Diu", "Tripura", "Uttar Pradesh", "Uttarakhand", "West Bengal")district_code string nullable — AISHE district code, from aishe/reference/states (examples: "095")institution_type_id string nullable — Institution type id, from aishe/reference/institution-types (examples: "01")@type string (default: "AisheDirectoryInstitution")id string requiredname string nullablecategory string nullablestate string nullabledistrict string nullableaddress string nullablewebsite string nullablemanagement string nullableestablished_year integer nullableinstitution_type string nullablelocation string nullableaffiliating_university_id string nullableaffiliating_university_name string nullableaffiliating_university_type 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 — 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.