SocialCrawl
Unified schema

Job schema

The unified SocialCrawl job posting schema. Every field, its type, per-platform availability, and a machine-readable JSON Schema, generated from the canonical Zod source.

Every SocialCrawl endpoint that returns a job posting gives you this exact shape, whatever the source platform. Write your parser once and the same code reads job data from every platform below. That is the unified schema: one contract instead of a dozen raw upstream formats.

Field reference

FieldTypeNullableDescription
idstringNoThe job's id on its source.
titlestringYesJob title.
urlstringYesURL of the posting.
company.idstringYesThe employer's id on the job source.
company.namestringYesEmployer name.
company.urlstringYesURL of the employer's page.
company.verifiedbooleanYesWhether the source marks the employer as verified.
locationstringYesJob location as the posting prints it.
listed_atstring or numberYesWhen the job was listed. An ISO 8601 time on most sources, but a relative label such as '4 days ago' on sources that publish no timestamp.
easy_applybooleanYesWhether the posting can be applied to without leaving the source.
remotestringYesWorkplace type as the source labels it, for example Remote, Hybrid or On-site.
employment_typestringYesEmployment type, for example Full-time or Contract.
experience_levelstringYesSeniority the posting declares. Null when it declares none.
descriptionstringYesFull job description. Present on job detail.
apply_urlstringYesWhere to apply. Present on job detail.

Extension fields (ext)

Platform-specific passthrough. Each field is present only on the platforms that expose it and is absent everywhere else, so treat every ext.* field as optional. These carry the richer, per-platform signals the unified leaves cannot hold, and the join keys that chain endpoints together.

FieldTypeNullableDescription
ext.is_promotebooleanYesWhether the posting is a paid promotion.
ext.applicant_countnumberYesNumber of applicants so far.
ext.skillsstring[]YesSkills the posting asks for.
ext.job_providerstringYesThe site the posting was originally listed on.
ext.salary_minnumberYesBottom of the salary range in salary_currency. The period (year, month, hour) is as the posting states it.
ext.salary_maxnumberYesTop of the salary range in salary_currency. The period (year, month, hour) is as the posting states it.
ext.salary_currencystringYesCurrency code of salary_min and salary_max.
ext.country_codestringYesCountry of the job as an ISO 3166-1 alpha-2 code.
ext.linkedin_company_namestringYesThe employer's company name on LinkedIn.
ext.industriesstringYesIndustry of the employer, as the posting lists it.
ext.job_functionstringYesJob function the posting is filed under.
ext.accepting_applicationsbooleanYesWhether the posting still accepts applications.
ext.boardstringYesThe job board the posting came from.

Platform availability

2 platforms return the Job shape. id are never null on any platform. The fields below vary: yes means the platform populates it (the value may still be null); a blank means the platform never provides it, so it is always null.

Platformcompany.idcompany.urlcompany.verifiedeasy_applyexperience_levelremote
Jobsyesyes
LinkedInyesyesyesyes

Machine-readable schema

Validate responses programmatically against the JSON Schema (2020-12):

/schemas/job.json

Point a validator (Ajv, jsonschema, or your framework's) at that URL, or hand it to an agent so it can check the shape without a live call.

Returned by

Endpoints with the Job / JobList archetype return this shape:

Jobs · LinkedIn

See how the same fields map to each platform's raw upstream names in the cross-platform field equivalence table.

On this page