Phase 1: Job Object

Creating a new SRE Job begins the process of requesting a student's records, but does not immediately provide the records.

post

Submit a new SRE job for processing.

get

Get the details of a specific job, identified by {jobId}.

delete

Delete the job. This also deletes all child resources (permissionRequest, sre, receipt).

Phase 2: Permission Request

Before a requester can access the sre object for a student, he must have obtained permission. This permission is tracked through this child resource called a "Permission Request", which contains details of the request, the status of the approval, and a token that is used to obtain the sre object in the next step. Because permission approvals will often require human intervention, these are always issued as a SIF delayed request.

get

Retrieves the list of permission requests.

post

Issues a new permission request. (Delayed response)

get

Fetches the details about the specified permission request.

Phase 3: SRE Object

Once the consumer has proper permissions, this phase requests the actual student record object. The provider should check that the requestToken is valid before delivering the xSre object.

get

Get the object

Phase 4: Receipt

Notifies the provider of the status of the record request, with additional receipt codes that the provider may be able to act upon. For example, this object could report that a student has been sucessfully enrolled in a receiving school district.

post

Post a new receipt object to the provider.