careers-page APIcareers-page.com ↗
Retrieve job application form definitions from careers-page.com career pages. Get all form fields, sections, labels, and field types for any listed job.
What is the careers-page API?
The careers-page.com API exposes one endpoint — get_application_form — that returns the complete application form definition for a specific job listing, including up to three field sections and every individual form field with its label, type, and display order. The response delivers 7 top-level properties covering field metadata, section groupings, job title, and whether terms acceptance is required to submit.
curl -X GET 'https://api.parse.bot/scraper/7793f2e4-d675-43c3-9794-947f0644b819/get_application_form?job_code=W3846469&company_slug=flowdesk-cx' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace careers-page-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: fetch a job application form and inspect its sections and fields."""
from parse_apis.careers_page_com_api import CareersPage, InputNotFound
client = CareersPage()
# Fetch the application form for a specific job listing.
try:
form = client.application_forms.get(company_slug="flowdesk-cx", job_code="W3846469")
except InputNotFound:
print("Job listing not found for the given company and job code.")
raise
print(form.job_title, "|", form.field_count, "fields")
print("Apply at:", form.apply_url)
print("Terms required:", form.terms_acceptance_required)
# Walk each section and its fields in display order.
for section in form.sections:
print(f"\n— {section.name} —")
for field in section.fields:
required_tag = "*" if field.is_required else ""
print(f" {field.label}{required_tag} ({field.input_type or 'n/a'}, id={field.field_id})")
# The flat fields list preserves the site's own ordering across all sections.
print(f"\nAll fields ({form.field_count}):")
for field in form.fields:
print(f" [{field.position}] {field.label} — section={field.section}, slug={field.slug or 'n/a'}")
print("\nexercised: application_forms.get")
Returns the application form for one job listing on a careers-page.com career page: the job title, whether accepting the terms and privacy policy is required to submit, and every form field in display order. Each field carries its site field id, label, field type, input type, response type, slug, required flag, answer choices (for dropdown/checkbox/multiple-choice questions; empty otherwise) and social-media network when the field is a social profile link. The same fields are also grouped into three sections: personal_information (identity fields such as full name, email, phone, nationality, birth date, gender, address, languages), profile (resume, attachments, social-media links, education and experience blocks) and details (cover letter, salary, notice period, years of experience and any employer-specific questions). The section grouping is derived from each field's type and slug because the site renders the form as one flat list; the flat fields array preserves the site's own order. Two round trips per call. A job code that does not exist for the company yields a not-found input error.
| Param | Type | Description |
|---|---|---|
| job_coderequired | string | Alphanumeric job code from the job URL, the segment after /job/ (e.g. one shape is a letter followed by digits). |
| company_slugrequired | string | Company slug from the career page URL, i.e. the path segment right after careers-page.com/ (lowercase letters, digits and hyphens). |
{
"type": "object",
"fields": {
"fields": "flat array of all form fields in the site's display order; each has field_id (string), label, section, field_type, input_type, response_type, slug, is_required (boolean), answer_choices (array of strings), social_media, position (integer)",
"job_code": "echo of the job code the form belongs to",
"sections": "array of three section objects (personal_information, profile, details), each with name and its fields in display order",
"apply_url": "public URL of the application page",
"job_title": "job title shown on the application page",
"field_count": "integer number of form fields",
"company_slug": "echo of the company slug the form belongs to",
"terms_acceptance_required": "boolean, true when the terms and privacy policy checkbox must be ticked to submit"
},
"sample": {
"data": {
"fields": [
{
"slug": "full_name",
"label": "Full Name",
"section": "personal_information",
"field_id": "965232",
"position": 0,
"field_type": "candidate_field",
"input_type": "text",
"is_required": true,
"social_media": null,
"response_type": "char",
"answer_choices": []
},
{
"slug": "description",
"label": "Cover Letter",
"section": "details",
"field_id": "965235",
"position": 5,
"field_type": "candidate_field",
"input_type": "long_text",
"is_required": true,
"social_media": null,
"response_type": "longtext",
"answer_choices": []
},
{
"slug": null,
"label": "Resume",
"section": "profile",
"field_id": "965236",
"position": 6,
"field_type": "resume",
"input_type": null,
"is_required": true,
"social_media": null,
"response_type": "char",
"answer_choices": []
}
],
"job_code": "W3846469",
"sections": [
{
"name": "personal_information",
"fields": [
{
"slug": "full_name",
"label": "Full Name",
"section": "personal_information",
"field_id": "965232",
"position": 0,
"field_type": "candidate_field",
"input_type": "text",
"is_required": true,
"social_media": null,
"response_type": "char",
"answer_choices": []
}
]
},
{
"name": "profile",
"fields": [
{
"slug": null,
"label": "Resume",
"section": "profile",
"field_id": "965236",
"position": 6,
"field_type": "resume",
"input_type": null,
"is_required": true,
"social_media": null,
"response_type": "char",
"answer_choices": []
}
]
},
{
"name": "details",
"fields": [
{
"slug": "description",
"label": "Cover Letter",
"section": "details",
"field_id": "965235",
"position": 5,
"field_type": "candidate_field",
"input_type": "long_text",
"is_required": true,
"social_media": null,
"response_type": "longtext",
"answer_choices": []
}
]
}
],
"apply_url": "https://careers-page.com/flowdesk-cx/job/W3846469/apply",
"job_title": "Account Executive (US Market) – E-Commerce SaaS Platform",
"field_count": 7,
"company_slug": "flowdesk-cx",
"terms_acceptance_required": true
},
"status": "success"
}
}About the careers-page API
What the API Returns
The get_application_form endpoint fetches the full application form for a single job on a careers-page.com-hosted career page. Given a company_slug (the path segment after careers-page.com/) and a job_code (the alphanumeric segment after /job/ in the job URL), the endpoint returns the job title, the public apply_url, a field_count, and the terms_acceptance_required boolean indicating whether applicants must tick a terms-and-privacy-policy checkbox before submitting.
Field and Section Structure
Form fields come back in two complementary shapes. The fields array is a flat list of every form field in display order; each entry carries a field_id, label, section, field_type, and input_type. The sections array organizes those same fields into three named groups — personal_information, profile, and details — each with its own ordered field list. This lets you either iterate all fields sequentially or address a specific section directly.
Input Parameters
Both required parameters are derived directly from the careers-page.com URL structure. The company_slug is lowercase letters found immediately after careers-page.com/ in the career page URL. The job_code is the alphanumeric code following /job/ in the listing URL — one documented pattern is a letter followed by digits (e.g. W3846469). Both values are echoed back in the response as company_slug and job_code for reference and validation.
Coverage Scope
This API is scoped to careers-page.com-hosted career pages. It covers application form structure and field definitions — not job description copy, compensation data, or candidate submission. Every field the form defines is present in the response regardless of section, making it straightforward to map required inputs before directing a user to the application flow.
The careers-page API is a managed, monitored endpoint for careers-page.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when careers-page.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official careers-page.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Pre-populate a custom application UI by reading field labels and input types from
get_application_formbefore rendering a form. - Audit which companies require
terms_acceptance_requiredconsent before application submission. - Compare application form complexity across roles by comparing
field_countvalues for differentjob_codeentries. - Build a job-application assistant that reads section structure (
personal_information,profile,details) to prompt candidates step by step. - Catalog required form fields per employer for a recruiting tool that automates form-filling workflows.
- Validate that a job listing is still accepting applications by checking whether the form definition and
apply_urlare returned.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does careers-page.com offer an official developer API?+
What exactly does `get_application_form` return for each form field?+
fields array includes a field_id, a human-readable label, the section it belongs to (one of personal_information, profile, or details), a field_type describing the kind of data collected, and an input_type describing the HTML input mechanism. Fields appear in the same display order shown on the live application page.Does the API return the actual job description, salary, or location details for a listing?+
Can I retrieve all job listings for a company rather than one form at a time?+
get_application_form endpoint takes a single job_code and company_slug and returns the form for that one listing. There is no bulk or list endpoint for fetching all active jobs under a company slug. You can fork this API on Parse and revise it to add a company-level job listing endpoint.What happens if I supply a `job_code` for a listing that no longer exists or has been closed?+
field_count is greater than zero and that apply_url is present before treating a response as a live application form.