...

See the About GraphQL APIpage for an introduction to the basic concepts of GraphQL, the schema, and examples of the functional operations used in the Fraud Data API (query, mutation, subscription).

...

The Fraud Data API

In the first initial phase ofdevelopment, the bi-directional Fraud Data API supports three main objectives to help identify and combat fraud: a) provide provides a mechanism for colleges to report locally-identified instances of application fraud to the CCCTC; b) the reporting of admission application data to a centralized database and the ability to run queries , as well as facilitate the ability to query against that data using an authorized MIS code with an AppID or CCCID. Internally, an algorithm determines if a submitted fraud application report also impacts another college in the district. If so, Superglue is leveraged to notify that college of the suspected bad actor. From a development perspective, the first phase of the Fraud Data project is to implement a centralized service that gathers fraud cross-references instances of identified fraud across the system for the purpose of that a bi-directional API and that mechanism to design a multi-purpose, bi-directional API solution for combatting different forms of fraud across the CCC systemIn turn, CCCTC algorithms work to determine if the submitted fraud information impacts other colleges across the system. If so, Superglue is leveraged to notify that college of the suspected bad actor.

By integrating the SuperGlue API to identify and share fraud data, colleges will be able to effectively extend the functionality of their own SIS systems and resources for increased efficiency. This is essential not only for meeting fraud reporting requirements, but decreasing overall costs and increasing time savings. Districts are encouraged to use this API for development within their own internal SIS system.

...

Eventually through continuous improvement, the API will be extended to also support other types of fraud data, including financial aid fraud. Participating districts are provided the Fraud Data API schema (GraphQL-based, described further below) and authorized access to the API during the implementation process with the CCCTCthe Fraud Data API schema (GraphQL-based, described further below) and authorized access to the API during the implementation process with the CCCTC.

Enabling bi-directional use of SuperGlue, whenever a college suspects or identifies admission application, enrollment, or financial aid fraud, information about that application can be shared with the CCC Tech Center, which in turn can suspend or block the profile effectively protecting all other colleges automatically.

Reporting Fraud Data Via API

...

Receive Fraud Notifications to Staging Table

As colleges report fraud by application ID (AppID), the CCCTC executes a workflow to identify the individual associated with the reported fraud (via their CCCID) and then locates any other submitted applications by that suspect CCCID. CCCTC then delivers these findings to the colleges that have also received a submitted application from that individual. These notifications are streamed Instances of application fraud reported to the CCCTC are used to identify other instances submitted by the same CCCID. These findings are then delivered to colleges as notifications to a new fraud-report staging table (for each college) via the SuperGlue College Adaptor. Each notification response will consist of the application ID (AppID), the applicant’s CCCID, and the MIS code of the college reporting the fraud (ReportedByMisCode).  Learn more about this process in the Receiving Fraud Notifications to a Staging Table section below.which can then be used to identify other instances, notify those colleges, and ultimately prevent the bad actor/individual (CCCID) from committing additional fraud against colleges in the future.

Below is a diagram of the API processes leveraged by SuperGlue and the College Adaptor.

...