Optional posting-details fields (loose validation)
Optional posting-details fields (loose validation)
When loose validation is enabled for your account, selected campaign-ordering fields become optional throughout the order journey. Candidates and recruiters can move past those fields without filling them in, and HAPI Elements submits the order with the omitted values accepted by the backend.
What changed
For each field your account marks as optional, HAPI Elements now:
- shows an
(optional)hint next to the field label instead of the required asterisk (*); - does not block the order-journey step when the field is left empty; and
- sends the request so the backend accepts the missing value.
If loose validation is not enabled for your account, nothing changes — all of these fields remain required exactly as before.
Which fields can be optional
The set of optional fields is driven by your account configuration and exposed
on the ATS settings under settings.campaigns.loose_validation. The fields that
can be made optional are:
| Field | Path |
|---|---|
| Years of experience | postingDetails.yearsOfExperience |
| Working location — address line 1 | postingDetails.workingLocation.addressLine1 |
| Target group — education level | targetGroup.educationLevel |
| Target group — seniority | targetGroup.seniority |
| Target group — industry | targetGroup.industry |
| Target group — job category | targetGroup.jobCategory |
City, postcode and country in the working location remain required.
Per order type
Optional fields are configured separately for each order type, under
settings.campaigns.loose_validation:
marketplace— applies when every product in the order is a Marketplace product;job_post— applies when every product in the order is a Job Post (My-Contract) product.
When an order mixes both types, the optional fields are the union of the two sets. If neither set lists any fields, loose validation is off and all fields stay required.
Notes
- This feature is enabled per account by VONQ — there is nothing to integrate.