# SIS Data Integration

The Unizin Order Tool requires data from your Student Information System to operate properly.

At present, Institutions are required to implement [version 2.0 of our SIS Integration](/products/content/unizin-order-tool/implementation/sis-data-integration/2.0-sis-integration.md) format.

## Integration overview <a href="#sisdataintegration-integrationoverview" id="sisdataintegration-integrationoverview"></a>

The Unizin Order Tool SIS Integration is a dataset of CSV files, generated nightly, that contains the latest data of courses, sections, enrollments, and other important data. The files are pushed by Institutions to an FTP server. The following document describes the contents of the CSV files required. It also describes the integration mechanism and requirements.

**Note**: distinct data integrations are required for your **production** and **user-acceptance testing** environments.

## File requirements <a href="#sisdataintegration-filerequirements" id="sisdataintegration-filerequirements"></a>

The following requirements apply to all the CSV files in a Unizin Order Tool integration.

* **Generated daily**. Data that impacts ordering changes every day.
* **Full dumps, not deltas.** We require you to effectively produce a snapshot (full dump) of the data integration every night.
* **Represent all data, even if optional.** Not all data requested in an integration file is required. However, the Unizin Order Tool expects you to represent optional data you choose not to share with the string "null."
* **Headers**. Your CSV files must have a header row on line 1. The tables below provide header names for each CSV file. Headers must be present for optional data.
* **Formatting.** The CSV files for SIS data should adhere to the following formatting rules:
  * All files should be UTF-8 encoded
  * Terminate lines with a UTF-8 Unix style newline
  * If no value is required or available for a field, use the *string* "null" as the value, not a blank
  * The escape character is a backslash (\\)
  * All values must be in double-quotes
  * All whitespace after the separator (,) will be imported. Avoid extraneous whitespace.

## FTP Server integration <a href="#sisdataintegration-ftpserverintegration" id="sisdataintegration-ftpserverintegration"></a>

Unizin uses [BrickFTP](https://brickftp.com/) as an FTP server service for the Unizin Order Tool's data integration. You will receive **two sets of credentials:** one for your production environment integration, one for your user acceptance testing environment integration.

Connection details:

* Hostname: [unizin.files.com](http://unizin.files.com/)
* Port: 22
* Username: as given, per environment
* Password: as given, per environment

Named sub-folders to the user's root folder will already be defined for each credential:

<table><thead><tr><th width="159">Folder</th><th>Function</th></tr></thead><tbody><tr><td><strong>/sis-data</strong></td><td>Institutions place their data integration files in this folder.</td></tr><tr><td><strong>/order-feed</strong></td><td>Unizin places an Institution's daily and weekly order report in this folder.</td></tr></tbody></table>

Notes on an institution's SIS data integration (to **/sis-data**):

* **Overwrite the CSV data files** if they happen to still be in the FTP folder.
* **Unizin Imports run at 8:00 AM UTC.** Uploading as near that time as possible ensures up to date data.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.unizin.org/products/content/unizin-order-tool/implementation/sis-data-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.