Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
panelIconId1f6a7
panelIcon:construction:
panelIconText🚧
bgColor#FFEBE6

This page was created to contain general notes/documentation for the CAS API and Slate integration that is CAS-agnostic. It is under construction.

...

Expand
titleSample text to request a new API account

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
titleSample text to request CAS/cycle added to existing API account:

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

...

The instruction to use CIDR subnets (e.g., 123.45.67.0/24) mean literally to use the .0/24 characters, even if the number you see in your machine’s individual IP address is something outside of that range. Setting this means there is no waiting when using these account credentials with Filezilla or Postman

Allowed Networks (Deprecated January 2024)

Expand
titleDetails

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.

Code Block
CLEAN SLATE

12.130.14.3, *
35.196.40.74, *
35.237.218.144, *
35.237.169.192, 
34.74.5.60, 
35.185.121.56, 
34.74.128.171, 
104.196.102.47


TUSMGP

12.130.14.3, *
35.196.40.74, *
35.237.218.144, *
35.237.169.192, * 
108.26.138.40, x
130.64.2.186, x
130.64.35.32, x
3.224.174.183, x
52.0.120.196, x
52.2.196.251, x
52.71.217.11, x
54.161.89.200, x
54.205.199.53, x
130.64.3.197 x

...

Deciding to use the CAS API vs. WebAdMIT API

Expand
titleExporting from WebAdmit in addition to the CAS API

Alex Sims (Mississippi State University)  2 months ago

Hey @Wyatt Best (ReWorkflow) (and @Peter Scorcia (Uni of Arizona)),
We've got a little mix of both going on at MSU.We utilize the Liaison CAS API to transfer data directly from the CAS applications into Slate. This is done via setting up "subscriptions" in POSTman which allows you to set event triggers that will bundle up the application data and transfer it to Slate via the SFTP servers and source formats. We have done this for VMCAS applications for 2 application cycles now. And I am literally neck-deep in implementing this same process for nursingCAS as I type (app goes live on 2/16 for our brand new Masters of Science / Nursing program). Liaison's documentation for this process is actually pretty good (https://help.liaisonedu.com/Integration/CAS_API/CAS_Slate_Integration )

However, as y'all mentioned, there are some things that just do not come in the data from the API--one example that I can think of from VMCAS was the "Academic Update Status". We could see in WebAdmit that a student had been sent back through the coursework verification process and was in an "Academic Update in Progress" status but there was no way of knowing that in Slate because that was not being transferred in any of the HUNDREDS of data points in the files from the API. So, I still set up exports from WebAdmit using the export manager to send a file to Slate every hour to set an Academic Update Status field in Slate to whatever that field was in WebAdmit.For our VMCAS applications, these are being reviewed in Slate but WebAdmit is still kind of being used as like a "system of truth" to find any discrepancies, like the academic update status.We also accept CASPA applications for our Physicians Assistant program. Those applications are reviewed within WebAdmit. Just in the last few months (October 2023, I believe), they decided that they would like those applications to be transferred to Slate. The reason for this is we have data integration between Slate and our SIS (Banner) to transfer applications at the point of admission. But, we don't have such integrations between WebAdmit and Banner. So, once these students were admitted in WebAdmit, someone was having to key those applications into Banner manually.
We utilize the WebAdmit Export Manager to schedule hourly exports from WebAdmit to Slate to transfer those "Offer Made" applications to Slate and automatically put a decision on the application in Slate which would trigger that app to transfer to Banner.With our nursingCAS implementation that we are currently building out, they intend to review the applications in WebAdmit. However, we are working with EAB for marketing purposes since this is a brand new program and we are trying to get the word out about it. EAB needs to know who in their population (via data transfers to/from Slate) have at least started an application. So, we are going to use the CAS API to transfer the application data to Slate for these applications. We haven't gotten to the point where any of these will actually have decisions. If we find that the decision data cannot be transferred to Slate via the API, then we will set up an hourly export from WebAdmit like we did for CASPA and through a combination of the API and hourly exports, we should have all of the data that we need.

Identifying and Interpreting Data Fields

...