Before you can begin working with the CAS API, your programs should be configured, and at least one program must be active.
Next, you'll need to establish the CAS API subscription to enable the delivery of application data and documents to Slate. This documentation contains the established subscription configuration that will work with the standard Source Formats.
Configuring in CAS
You can set up the integration against the CAS' Prelaunch (test) environment in advance of deploying it for live applications from the Production environment. At schools where CAS participation is well established, program configuration is likely already complete. Applicants can only apply to active CAS programs (in either the Prelaunch or Production environment), so it is necessary to have at least one program activated to collect records for the development and testing of the integration.
Another relevant consideration is timing relative to a new CAS admissions cycle. A common approach is to develop a new integration against the CAS Prelaunch environment in the months before a new CAS admissions cycle opens up to live applicants, then migrate that integration to the CAS Production environment. This is the recommended approach. Alternatively, a school may decide to develop a new integration approach against the CAS Production environment for a CAS admissions cycle that is already live and accepting applications. This alternative approach adds complexity with the cutover from the previous integration to the CAS API integration. This alternative approach may be appropriate for schools that do not have another CAS-Slate integration established (i.e., they're manually entering each record by hand).
For more information, also see the Slate Knowledge Base.