/internshala/jobs

POST /api/internshala/jobs

Price: 10 credits

Get one Internshala (internshala.com) job by URL: title, status, company with its website, about text and hiring activity, locations, start date, annual salary and its breakdown, experience, apply-by and posting dates, applicant count, full description, skills, who can apply, openings and similar jobs

How to use it

Pass the url from internshala/jobs/search. Pass company_id to internshala/companies for the company profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Internshala job URL or slug (examples: "https://internshala.com/job/detail/accountant-job-in-multiple-locations-at-team-management-services-tms1790762893", "accountant-job-in-multiple-locations-at-team-management-services-tms1790762893"; minLength: 1; maxLength: 300)

Response

• @type string (default: "InternshalaPosting")
• id string required
• url string required
• alias string nullable
• kind string nullable
• heading string nullable
• status string nullable
• company_name string nullable
• company_id string nullable
• company_url string nullable
• company_image string nullable
• company_website string nullable
• company_about string nullable
• company_hiring_since string nullable
• company_opportunities_posted integer nullable
• company_candidates_hired integer nullable
• is_actively_hiring boolean nullable
• locations array (default: [])
• is_remote boolean nullable
• work_mode string nullable
• office_days_per_week integer nullable
• start_date string nullable
• duration string nullable
• experience string nullable
• salary string nullable
• salary_min number nullable
• salary_max number nullable
• salary_period string nullable
• salary_details string nullable
• apply_by_at integer nullable
• posted_at integer nullable
• labels array (default: [])
• is_part_time boolean nullable
• employment_types array (default: [])
• category string nullable
• industry string nullable
• applicant_count integer nullable
• is_early_applicant boolean nullable
• description string nullable
• skills array (default: [])
• who_can_apply string nullable
• other_requirements string nullable
• additional_information string nullable
• perks array (default: [])
• openings_count integer nullable
• similar_postings array (default: [])
  • @type string (default: "InternshalaSimilarPosting")
  • id string required
  • url string required
  • alias string nullable
  • company_name string nullable
  • company_id string nullable
  • locations array (default: [])
  • salary string nullable
  • duration string nullable
  • experience string 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 job 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.