Slate: Housing Applications

Last updated: October 5, 2026

Housing.Cloud is capable of generating an Application CSV file with the intent of being consumed by Slate Admissions. The CSV transmission process will follow Housing.Cloud's standard SFTP process.

Configuration

  1. Institution creates a Custom Profile Field in Housing.Cloud called SlateAppTermCode
  2. Institution updates the Profile SFTP import to include this value
    1. The value should be the Term Code for which this person is required to apply for housing
  3. Institution will specify the transfer cadence of the file (e.g. every 30 minutes)
    1. The cadence can be any value supported by a Cron string, but it must be equal to or greater than every 10 minutes

File Inclusion Process

  1. Housing.Cloud will fetch all active and upcoming Cycles and extract the list of External Term Codes
  2. Housing.Cloud will fetch all Profiles where a Profile's SlateAppTermCode is included in the list of the Cycles' External Term Codes

  3. Housing.Cloud will fetch all Applications (if available) belonging to the Profiles determined from step 2 and include the Profile in the export file

     

File Format

Column Header Data Type Description
sisId string A Profile's sisId in Housing.Cloud
applicationStatus enum string Values: NOT_STARTED, STARTED, COMPLETED
ANY ADDITIONAL PROFILE FIELDS string Any configured Profile Fields*

 

Notes:

  • Housing.Cloud can be configured to include Custom Profile Fields in the export file. If a Profile does not have a value for the provided Custom Profile Field(s), then an empty string will be utilized.

    • In the attached example, the slateApplicationId column is a configured Custom Profile Field

     

 

 

Attachments