| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This page was created to contain general notes/documentation for the CAS API and Slate integration that is CAS-agnostic. It is under construction. |
...
| Note |
|---|
An Institution Manager (IM) for each CAS must reqest request either a new account or that access be given to an existing account for their CAS. However, the CAS API Account itself can have a different “owner” than the IM. If the owner will be different than the IM, the owner will need to have access to WebAdMIT prelaunch and/or production in order to be given access via the CAS API Account to those environments. |
...
Once access for a CAS/organization is added to the account, it will “roll over” each year when the new cycle is added, so this process only needs to happen once per CAS/organization.
Access Timing for access to each cycle’s prelaunch environment and production environment will depend on when it is “opened” as part of the cycle (see Cycle Turnover Process). Typically, the Prelaunch API becomes available when the Configuration Portal opens, and Production API becomes available when applicants can select particular schools.
Sample Tickets
Send to apisupport@liaisonedu.com.
| Expand | ||
|---|---|---|
| ||
Subject: Request to create new API account Hello, I am writing to request a new API account be created for the following CAS and institution. If possible, I’d like to reqest that the account username be [xxxxx]. Institution Manager name and email address: [xxxxx] Name of user to receive CAS API access: [xxxxx] CAS API user phone number: [xxxxx] CAS API user email address: [xxxxx] The name of your institution (university/college/school/etc.): [xxxxx] The CAS, one or many, that you're interested in (e.g. BusinessCAS): [xxxxx] The CAS admissions cycles you're interested in (e.g., 2020-2021 and 2021-2022): [xxxxx] The environment: [Prelaunch or Production] |
| Expand | ||
|---|---|---|
| ||
Subject: Request adding CAS to existing API account Hello, This year we will be setting up a CAS API integration for CASPA for Tufts University (program ID 346115 for 23-24). We have existing API accounts for other integrations so I am writing to request that access to CASPA be granted to the below API accounts. Prelaunch account username: TuftsUniPre Production account username: TuftsUni |
...
Username | Environment | CAS (Org) and Cycles |
|---|---|---|
TuftsUni | Production | SOPHAS, PTCAS |
TuftsUniPre | Prelaunch | PTCAS |
TuftsVet | Production | VMCAS |
REQUESTED | Prelaunch | VMCAS |
CAS/
...
Liaison Service Account Configurations (Slate)
To enable automated delivery of CAS application data through the API, Slate requires each instance to have a “CAS/Liaison Service Account” (functionally a “user”) which is assigned a role that allows SFTP access. This “user” is what holds the permissions, allowed networks, and other security settings to allow the data to be transferred from the CAS environment into the Slate environment via SFTP.
...
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
Allowed Networks (Deprecated January 2024)
Below are the IP addresses that are included in the “allowed networks” of existing CAS/Liaison Service accounts for future reference. It is unclear which exactly are used by the Liaison systems, the following list is provided for reference/troubleshooting.
...