POST /api/internshala/jobs/search
Price: 10 credits
Search Internshala (internshala.com) jobs by keyword, category, city, work from home, part time, experience and minimum salary: id, URL, title, company, locations, salary, experience, summary, skills, labels and posting date
Leave keyword empty to browse by filters alone. categories and city take names as Internshala lists them, and a name it does not list is rejected. experience fresher lists jobs open to freshers. Pass a returned url to internshala/jobs for the full posting.
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; max: 5000)keyword string nullable — Keyword (examples: "accountant"; minLength: 3; maxLength: 100)categories array nullable — Job categories (examples: ["Accounts","Finance"]; maxItems: 10)city string nullable — City (examples: "Pune"; minLength: 2; maxLength: 60)work_from_home boolean — Only work-from-home jobs (default: false)part_time boolean — Only part-time jobs (default: false)experience string nullable — Candidate's experience (one of: "fresher", "1", "2", "3", "4", "5", "5plus")min_salary_lakhs integer nullable — Minimum annual salary in lakh INR (examples: 5; min: 1; max: 12)@type string (default: "InternshalaPostingSummary")id string requiredurl string requiredalias string nullablekind string nullablecompany_name string nullablecompany_image string nullableis_actively_hiring boolean nullablelocations array (default: [])is_remote boolean nullablesalary string nullablesalary_min number nullablesalary_max number nullablesalary_period string nullableduration string nullableexperience string nullablesummary string nullableskills array (default: [])labels array (default: [])is_part_time boolean nullableis_early_applicant boolean nullableposted_at integer nullable422 — Internshala does not list that category or city 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.