...
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 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.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
For colleges that have implemented the College Adaptor, the Fraud Data API leverages SuperGlue to stream fraud notifications to a new dedicated staging table. |
...
From Your Postman Workspace… Step 1: Expand the Fraud Report collection and click on the Fraud Report OAuth file.. Step 2: See the Fraud Report OAuth file open in a tab on your Workbench. Step 3: Ensure the appropriate environment is selected. In the adjacent example, the “GraphQL:Pilot” environment is selected (active). Step 4: Click the Send button to generate the access token. 5. The ‘access_token’ appears in the lower half of the body of the Fraud Report OAuth tab, which is then embedded for authorization for the next web request or post. Access Token The 'access_token” becomes the Each time you refresh your authorization, the new ‘access_token’ is automatically saved to the header for the next API operation you intend to execute. Each token expires in 300 seconds (5 mins). |   |
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
The A primary function of the API is to enable colleges to report facilitate the process of submitting suspected or identified fraudulent admission applications to the CCCTC 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. |
Submitting a Fraud Report Via API
The process for reporting fraud information to the CCCTC via the API is known as the FraudReportSubmit operation. The full schema is documented in the Apollo sandbox.
In GraphQL general terms, the components of the GraphQL operation are quite basic, which the documentation provided in the Apollo sandbox is comprehensive. The FraudReportSubmit query is a mutation type object that requires an Input argument (FraudReportSubmitInput!) where at least one variable input field must be provided, and a structured payload response is defined (FraudReportSubmitPayload). For the majority of fraud report submissions, only the input of the application Id (AppID) is truly needed; however additional input fields may also be added to the operation.
...
The FraudReportSubmit Operation
In the screenshot below, Below is an example of a basic FraudReportSubmit operation is built -out in the Apollo sandbox.
 | In the Operation section, the root mutation, a FraudReportSubmit mutation is built showing FraudReportSubmit, has been selected with the default FraudReportSubmitPayload fields displayed. In the Documentation column, the Input argument - FraudReportSubmitInput - is selected and expanded showing the fields that can be used for the required input. In the Variables table, the “appId” field as been added as the only input variable for this basic operation (currently displaying a null value).
 |
...