When sending a candidate to your integration, Custom Fields may not always be enough. You might need to request additional data that depends on previously submitted information. This can be achieved with a two-step flow: first, set up the Candidate Custom FieldsCandidate Custom Fields. Once that primary form is submitted, Jobylon ATS will forward it to you as per the usual flow. You can then process this data and build a secondary form that requests additional fields based on the information submitted in the first form.

Please note that Dynamic Custom Fields are not automatically available. To start using them, you must first contact your Jobylon contact.

When using Dynamic Custom Fields, once the user submits the first form, Jobylon ATS will immediately send a Candidate Webhook to the partner, as described in Webhookshere. This webhook will include, among other fields, the following:

Jobylon expects an immediate response to this webhook. The response must return a 200 status code and a JSON including a URL where Jobylon can access the dynamic fields.

Response example:

The ATS will attempt to access the returned URL up to 5 times, with a 3-second interval between each attempt. Once the form is available, Jobylon ATS will show it to the user. If the form is still unavailable after the fifth attempt, an error message will be displayed to the user and the flow is interrupted.

Jobylon expects the dynamic form to be present in the returned URL, in JSON format. All the fields must be within the fields object and follow the exact same structure as shown in Api Reference/OpenAPIapi for Candidate Config. For example:

Once the user saves the secondary (dynamic) form, Jobylon ATS sends a second webhook to the partner with the following fields:

This is a separate mechanism from Candidate UpdatesCandidate Updates. Dynamic Custom Fields let the partner request a second form right after the first send; Candidate Updates let a Jobylon user later edit and resubmit a candidate already sent.