Data
If several people rent together, send the data of each co-tenant in the same application. See Candidates who rent together.
The API accepts more fields than the score uses today, such as the employment
regime and the documents. You can send them now: Vivara will use them as the
score evolves, without you changing your integration. See Coming
soon.
Unknown employment situation
OmitworkingStatus when you do not know the candidate’s employment situation.
Send their annual net income in netAnnualIncomeAmountInEuros:
personalId if you know it. If you do not, omit it too.
Explicit null is also accepted for both fields and means the same as omission.
The API normalizes missing values to null; the GET response includes both
personalId and workingStatus, with null when not declared.
For self-employed candidates, explicitly send workingStatus: "self-employed"
with form100 and form130, instead of netAnnualIncomeAmountInEuros.
These rules apply to both POST and PUT. PUT replaces all candidatures and members:
if a member previously had a working status and you now omit it or send null,
the new declaration has no working status. It does not keep the previous value.
Send every candidature and member you want to retain, including all known data.
Documents
Documents are optional. Send them when you have them to move the candidate to the Accredited tier:- The ID document, to accredit the ID number
- The income documents for the candidate’s employment situation, to accredit the income
Adding data later
You do not need everything at once. A common sequence is:- Score all the candidates for a listing with their declared income.
- Call the most promising ones and ask for their ID number.
- Collect documents from the candidates you are about to choose.