POST /candidateDocumentTypes/{candidateDocumentTypeId}/uploadNew response : 409 Conflict
An auto check is running on the parts of this document (NOT_ALLOWED_UNTIL_DOCUMENT_IN_PROCESSING). The parts are frozen while they are being validated; retry the upload once the check has finished.
GET /documentTypes/{id}Added: includeSubmission in query
To include document type 'submission' relation: the post-submission rules applied when a document of this type is validated
Changed response : 200 OK
Request was successful
Changed content type : application/json
Added property submission (object)
Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
Property rules (array)
Rules evaluated in order. Rules of a document type shared with another company of the group are not applied
Items (object): > A post-submission rule: conditions to evaluate and actions to apply when they match, or on every validated document when there are no conditions
Property id (string)
Unique identifier for the entity
Property conditionsType (string)
Whether every condition has to match or only one of them. Ignored when there are no conditions
Enum values:
orandProperty conditions (array)
Empty for a rule that applies to every validated document of this type
Items (object): > One condition of a post-submission rule
Property type (string)
Where the reference is read from.
fieldsis the parsed document,contextis the candidate around it
Enum values:
fieldscontextProperty reference (string)
Key to read. For
fieldsit is a document parser reference, dotted for nested values. Forcontextit is a candidate key,cf_<reference>for a candidate custom field ordcf_<reference>for a document custom field
Property operator (string)
How the read value is compared
Enum values:
isEmptyisNotEmptyisEqualisNotEqualcontainsnotContainsProperty value (object)
Value to compare against. Not needed by
isEmptyandisNotEmpty
One of:
Items (string):
Property actions (array)
Items (object): > One action applied to the candidate when the rule matches
Property type (string)
What to do with the candidate
Enum values:
sendNotificationaddDocumentTyperemoveDocumentTyperemoveFormapplyPresetProperty value (string)
Id of the entity the action targets: a document type, a form, a candidate preset or a notification scenario, depending on
type
Property metadata (object)
Extra properties of the requested document, read by
addDocumentTypeonly
PATCH /documentTypes/{id}Changed content type : application/json
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
Changed response : 200 OK
Request was successful
Changed content type : application/json
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
POST /containers/{candidateDocumentTypeId}/uploadNew response : 409 Conflict
An auto check is running on the parts of this document (NOT_ALLOWED_UNTIL_DOCUMENT_IN_PROCESSING). The parts are frozen while they are being validated; retry the upload once the check has finished.
GET /scenariosChanged response : 200 OK
Request was successful
Changed content type : application/json
Changed items (object): > Scenario included relations
Changed property documentTypes (array)
Scenario document types
Changed items (object):
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
POST /scenariosChanged response : 200 OK
Request was successful
Changed content type : application/json
Changed property documentTypes (array)
Scenario document types
Changed items (object):
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /scenarios/{id}Changed response : 200 OK
Request was successful
Changed content type : application/json
Changed property documentTypes (array)
Scenario document types
Changed items (object):
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
PATCH /scenarios/{id}Changed response : 200 OK
Request was successful
Changed content type : application/json
Changed property documentTypes (array)
Scenario document types
Changed items (object):
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /candidateDocumentTypes/{id}Changed response : 200 OK
Request was successful
Changed content type : application/json
Changed property documentType (object)
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /registration-pagesChanged response : 200 OK
Request was successful
Changed content type : application/json
Changed property documents (array)
Related documents
Changed items (object):
Changed property documentType (object)
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /registration-pages/{id}Changed response : 200 OK
Request was successful
Changed content type : application/json
Changed property documents (array)
Related documents
Changed items (object):
Changed property documentType (object)
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /candidateDocumentTypesChanged response : 200 OK
Request was successful
Changed content type : application/json
Changed items (object): > Candidate Document Type properties
Changed property documentType (object)
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
POST /documentTypesChanged content type : application/json
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
Changed response : 200 OK
Request was successful
Changed content type : application/json
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.
GET /documentTypesAdded: includeSubmission in query
To include document type 'submission' relation: the post-submission rules applied when a document of this type is validated
Changed response : 200 OK
Request was successful
Changed content type : application/json
Changed items (object):
submission (object)Actions applied to the candidate once a document of this type is validated. They run after the parsed values have been written back onto the candidate and before the candidate status is recalculated, so integrations see the result of the rules.