| 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. |
...
Term | Definition |
|---|---|
CAS association | The group that owns and manages the CAS (e.g., APTA for PTCAS, ASPPH for SOPHAS, etc.) |
Organization ID | Associated with the school/institution (e.g., Tufts University). Indicates the institution’s entity within the CAS/cycle. A unique ID used in setting up API accounts and subscriptions. Remains the same across cycles. Tufts has multiple Organization IDs; Vet is different from CASPA, and they are different from each different location PT has. |
Application Form ID | Associated with the CAS/cycle (e.g., the PTCAS application for 23-24), represents the configurations made by the CAS association for their centralized application for that cycle, a unique ID used in setting up API accounts and subscriptions. Each year/cycle it will change for the CAS, but within that cycle it is the same for any program within that CAS (i.e., the individual DPT programs use the same application form ID because it is for PTCAS and not the program itself). |
Program ID | Associated with each program within the organization. Some CAS applications will only have one program (e.g., CASPA) but others will have multiple (e.g. SOPHAS). Used to generate the CAS/Liaison Application ID (the unique identifier used for matching data sent from the CAS to Slate on the application, vs. the person) which is key for both the data and document integrations. In the API this is stored in the progMate.progSele0.programID field, in WebAdMIT it is found under Designation > Program Identifier. |
Prelaunch is a "staging" environment that allows you to configure programs for the new cycle without impacting the current cycle. | |
The "live environment" is where you perform your applicant review processes. | |
CAS Applicant ID | Unique to the person; consistent across cycles and CAS. Note that Liaison does not generate a single application ID; best practice is to concatenate the Applicant ID with the Program ID (progMate.progSele0.programId) before import. |
...
| 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 request 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 |
...
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
Allowed Networks (Deprecated January 2024)
| Expand | ||
|---|---|---|
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.
|
...