/internshala/companies/openings

POST /api/internshala/companies/openings

Price: 20 credits

List the open internships and jobs of one Internshala (internshala.com) company by URL or id: id, URL, title, locations, stipend or salary, duration, experience, summary, skills, labels and posting date

How to use it

Pass company_id from internshala/internships, internshala/jobs or internshala/companies. Jobs come before internships. Pass a returned url to internshala/internships or internshala/jobs for the full posting.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Internshala company URL or id (examples: "https://internshala.com/company/upgrad-learnings-private-limited-1788944144/careers/"; minLength: 1; maxLength: 300)
• count integer required — Max number of results (min: 1; max: 1000)
• kind string — Internships, jobs or both (default: "all"; one of: "all", "internships", "jobs")

Response

• @type string (default: "InternshalaPostingSummary")
• id string required
• url string required
• alias string nullable
• kind string nullable
• company_name string nullable
• company_image string nullable
• is_actively_hiring boolean nullable
• locations array (default: [])
• is_remote boolean nullable
• salary string nullable
• salary_min number nullable
• salary_max number nullable
• salary_period string nullable
• duration string nullable
• experience string nullable
• summary string nullable
• skills array (default: [])
• labels array (default: [])
• is_part_time boolean nullable
• is_early_applicant boolean nullable
• posted_at integer nullable

Errors

• 422 — 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 — Internshala has no company under that URL 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.