Convert an applicant into a tenant
Creates a tenant record from an approved application, copying over the applicant's name, contact details, Social Security number, driver's licence, date of birth and current address, then links the tenant back to the application. Requires the rental_applications:write permission.
Authorization
AuthorizationstringrequiredPath parameters
idstringrequiredThe rental application to work with. A Snowflake id, sent as a decimal string.
Response
200 · The tenant. When the application had already been converted, the existing tenant is returned rather than a new one being created.
idstringThe new tenant.
activebooleanWhether the tenant record is active.
firstNamestringTenant's first name, copied from the application.
lastNamestringTenant's last name.
emailstring · emailTenant's email address.
phonestringTenant's phone number, formatted for display.
createdstring · date-timeWhen the tenant was created, in the company's timezone.
updatedstring · date-timeWhen the tenant last changed, in the company's timezone.
lastSeenstring · date-timeWhen the tenant last used their portal. Absent when they never have.
lastPortalInvitestring · date-timeWhen a portal invite was last sent. Absent when none has been.
chatIdstringThe tenant's chat thread. Absent when none exists.
languagestringThe tenant's preferred language code. Absent when none is set.
ssnstringThe tenant's Social Security number, digits only. Absent when none is on file.
driversLicenseobjectDriver's licence details carried over from the application. Absent when none are on file.
dateOfBirthstring · dateTenant's date of birth. Absent when none is on file.
genderenum<string>The tenant's gender, when the Tenants service holds one.
emergencyContactsobject[]Emergency contacts held on the tenant record.
400 · The application's decision is not `approved`. Set the decision first.
400 · The application has no first name, or one shorter than two characters. A tenant cannot be created without it.
409 · The Tenants service refused to create the tenant because it clashes with an existing one. The `reason` member carries what it said.
401 · The access token is missing, expired, or not valid.
403 · The caller is authenticated but does not hold the `rental_applications:write` permission.
404 · No rental application with this id exists, or it belongs to another company. Both cases look identical so that ids cannot be probed across companies.
If the application already points at a tenant that still exists, that tenant is returned and nothing new is created.
If another tenant in the company already uses the applicant's phone number, the tenant is created without a phone number rather than the call failing.