API DOCUMENTATION / SOURCE VALUES AND DERIVED VALUES
Source values and derived values
Read state envelopes and keep source-preserved posting data distinct from normalized public fields.
State-bearing values retain provenance
Fields such as title, employer, description, URLs, and pay can be represented with a state. A known value carries value; source_omitted reports source absence; source_unmapped may carry null and evidence; derived values include evidence. Preserve both state and evidence when your UI explains a result.
Normalized fields are bounded
The DTO includes a defined set of job and posting fields. Benefits, hours, education or experience requirements, skills, responsibilities, qualifications, and hiring-team contacts are not separate normalized fields in this DTO.
Optional source_data is source-dependent
With include=source_data, the jobs list passes through stored source_data and source_rights; detail normalizes optional source_data to named snake_case properties. The inner payload can vary by source and is not a uniform enrichment schema.
Keep original and interpreted values separate
When a product derives search categories or recommendations from source text, store those as your own interpretation. The checked public DTO does not establish an enrichment service, a model, or a completeness guarantee.
Continue in the reference
Check related request behavior before you build.
View route status and methods Discuss API requirements