Create Application
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
The Propexo unique identifier for the application template. The Rentvine application template dynamically defines which fields are required for each applicant/application: whether a field is active, disabled, required, or optional. A template may also allow some enums to be modified or for entire fields to be relabeled/repurposed. The functionality of a template is extensive and will likely require that you work with your customer to define a custom template for your application use case
The desired move-in date to the unit listed in the application
The first name associated with the applicant. Required if lead_id is not specified
The last name associated with the applicant. Required if lead_id is not specified
The type of applicant. Depending on the Rentvine template, this field can be customized to be either required or optional. You will need to work with your customer directly to configure this field to your application requirements. Although the field itself can be made optional/required, the value must be one of the available choices and cannot be modified as part of the template
The Propexo unique identifier for the employee. Employee must have a role of LEASING_AGENT. Required if lead_id is not specified
The Propexo unique identifier for the lead source. Required if lead_id is not specified
A unique ID you would like to associate with the applicant. This is not the Sample1 applicant ID. Required if lead_id is not specified
The name of your organization. Sample1 uses this for associating an applicant. Required if lead_id is not specified
The desired move-out date to the unit listed in the application