...

...

Introduction

The Fraud Data API is a SuperGlue-based solution (API) that supports bi-directional communication and sharing of suspected admission application, enrollment, or financial aid fraud with the CCC Technology Center, which in turn can suspend or block the individual’s profile, effectively protecting all other colleges automatically. Developed using GraphQL API technology, the first phase of this service will leverage the SuperGlue framework to amass a fraud data repository from college reports and then stream notifications out to other affected colleges. Eventually through continuous improvement, the API will be extended to support other types of fraud data, including enrollment and 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 CCCTC.

...

The reporting of locally identified fraud data from an individual college or district to the CCC Technology Center (CCCTC) is managed via the Fraud Data API. Everything needed to submit fraud reports is documented in the schema (see the API Documentation section below), as well as through custom Postman files configured specifically for the fraud data operations. More information and detailed examples of the FraudReportSubmit mutation are provided in the Submitting a Fraud Report Via APIsection of this guide.

Receive Fraud Notifications to Staging Table

...

An option for colleges that have not yet implemented the SuperGlue College Adaptor, the API facilitates the ability to query the fraud table directly using a CCCID, an AppID, or an authorized MIS code(withRecipientMisCode). A successful response is returned if the CCCID used in the query matches any other application(s) submitted to the authorized MIS code. The process for querying the API directly is described in the Querying Fraud Data via APIsection of this guide.

...

Advantages of Using Postman

...

With your API account created with the proper credentials in place, the request below returns a JSON block including an “access_token” field. This token becomes the Bearer required in the Authorization head for secured requests to the API. (Reminder: Your API account is provided by the CCCTC during the implementation process.)

...

From Your Postman Workspace… 1: Expand the Fraud Report collection and click on the Fraud Report OAuth file.. 2: See the Fraud Report OAuth file open in a tab on your Workbench. 3: Ensure the appropriate environment is selected. In the adjacent example, the “GraphQL:Pilot” environment is selected (active). 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 Bearer required in the Authorization head for secured requests to the API. (Reminder: Your API account is provided by the CCCTC during the implementation process.) 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).

...

Explore the schema documentation for the FraudReportSubmit mutation and see the available Input fields.

...

...

...

Colleges that have not yet implemented the SuperGlue College Adaptor can query fraud data related to their college directly via the Fraud Data API. The schema describes this operation as FraudReportQuery, the query interface for retrieving a FraudReport object, which is the 10 field response for a student and/or application.

...