POST /api/studyinindia/institutes/search
Price: 5 credits
Search the Indian institutions that recruit international students on Study in India, by part of the name, state and scholarship, or ordered by NIRF rank. Each institute carries its AISHE code, state, city, type, NIRF category and rank, areas of study, study modes and website.
Use this to find an Indian college or university and its AISHE code; pass the `id` to studyinindia/institutes for its profile, contacts and living costs.
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)name string nullable — Part of the institute name (examples: "Indian Institute", "Parul University")state string nullable — Indian state or union territory of the institute (one of: "andhra_pradesh", "assam", "bihar", "chandigarh", "chhattisgarh", "delhi", "goa", "gujarat", "haryana", "himachal_pradesh", "jammu_kashmir", "jharkhand", "karnataka", "kerala", "madhya_pradesh", "maharashtra", "meghalaya", "nagaland", "odisha", "puducherry_pondicherry", "punjab", "rajasthan", "sikkim", "tamil_nadu", "telangana", "tripura", "uttar_pradesh", "uttarakhand", "west_bengal")scholarship_only boolean — Only institutes offering a scholarship (default: false)sort string nullable — Order of the results (one of: "name_asc", "name_desc", "city_asc", "city_desc", "nirf_rank")@type string (default: "StudyInIndiaInstitute")id string requiredname string nullablestate string nullablecity string nullableinstitute_type string nullablenirf_category string nullablenirf_rank string nullabledisciplines array (default: [])study_modes array (default: [])website string nullableacademic_year string nullablehas_scholarship boolean 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.