Turn AQA Centre Services into an API

What you can build on Centre Services

• Check post-results request statuses

  Build this

  Reads View or cancel requests under Post-results services: each review of marking, copy of a marked paper or access to scripts request, with its status.

  Takes

  Series (optional), status (optional)

  Returns

  Candidate number, candidate name, component, service, submitted date, status

• Get post-results outcomes

  Build this

  Reads the outcomes (decisions) on Centre Services for completed post-results requests, with each mark change, its reasons and any new grade.

  Takes

  Series, completed since (optional)

  Returns

  Candidate number, component, service, original mark, new mark, reasons, original grade, new grade, outcome date

• Get the NEA moderation sample

  Build this

  Reads a component in centre marks submission (CMS): whether its marks were sent with Submit to AQA and which candidates CMS chose for the moderation sample.

  Takes

  Series, component code

  Returns

  Component, submitted to AQA, candidates entered, marks entered, sample candidates (number, name, mark)

• Request access to a marked script

  Build this

  Opens Access to scripts under Post-results services, chooses Request by candidate and requests the Original script for one component.

  Takes

  Series, candidate number, component, learner consent held

  Returns

  Candidate number, component, service, status

Automate Centre Services with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• New post-results outcomes, every morning after results day

  Build this

  Starts

  Every weekday at 7:30 from results day until your last outcome is in

  Step 1

  Check post-results request statuses for the series.

  Step 2

  Keep the requests that are Completed now but were not on the last run.

  Step 3

  Get the outcomes for those requests, with any mark and grade change.

  Step 4

  Email you the list, grade changes first.

• Grade changes posted to your MIS

  Build this

  Starts

  Every day at 18:00 during the post-results period

  Step 1

  Get the post-results outcomes completed since yesterday.

  Step 2

  Keep the outcomes where the grade changed, and stop when there are none.

  Step 3

  Post candidate number, component, service, new mark, original grade and new grade to your MIS through its webhook.

• NEA components not yet submitted to AQA

  Build this

  Starts

  Every Monday at 8:00 while CMS is open for the series

  Step 1

  For each component code you name, get its status in CMS.

  Step 2

  Keep the components not submitted to AQA, and those with candidates missing a mark.

  Step 3

  Email you the list with the count of marks still to enter.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Check post-results request statuses” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "onlineservices.aqa.org.uk/check_post_results_requests",
    "input": {
      "series": "June 2026",
      "status": "In progress"
    }
  }'

{
  "status": "completed",
  "data": {
    "series": "June 2026",
    "requests": [
      {
        "candidate_number": "4127",
        "candidate_name": "Avery Northwind",
        "component": "8461/1H",
        "service": "Review of marking",
        "submitted": "2026-08-24",
        "status": "In progress"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

Centre Services’s own options

AQA documents no API for Centre Services. Entries go to AQA as EDI files from your school's MIS through JCQ's Data Transport Application, and NEA marks can be sent the same way, after which you still click Submit to AQA in CMS. Results documents, post-results requests and their outcomes are handled in Centre Services.

Read on November 12, 2026: Make entries with EDI and basedata, Submit marks and grades, Exams Officer update August 2026.

Signing in to Centre Services

Centre Services signs you in with your email address and password, then a multi-factor code sent to your phone, or an authenticator app if AQA switches you to one after your Head of Centre approves. Each person has their own account. With Fous you sign in once through Centre Services' own sign-in with your own account: the login is sealed with AES-256.

Worth knowing

Download what you need to keep

Outcomes and copies of reviewed scripts stay on Centre Services for two years. Copies requested through Access to scripts from the previous calendar year are removed each April.

EDI marks still need Submit to AQA

Marks sent by EDI appear in CMS, but the submission is complete only when you click Submit to AQA. That click is also when CMS generates your moderation sample.

Consent before access to scripts

You must have the learner's consent before you request access to their script, using JCQ's student written consent form.

Results documents are embargoed

Results documents arrive on restricted release day as a zip folder and must not be shared with learners, teachers or parents until 8.00am on results day.

More in Education, research and nonprofit

• Slate
• Naviance
• Common App for Recommenders
• National Student Clearinghouse secure site
• Edexcel Online
• FSA Partner Connect
• Submit learner data
• VA Enrollment Manager
• Sponsorship Management System
• Infinite Campus
• PowerSchool SIS
• EDOF
• Arbor MIS
• SLC HEP Services
• Parchment
• UCAS adviser portal
• Benevity Causes Portal

Other industries: DTE Energy online account, METRO Online-Kundenkonto, Axis Corporate Internet Banking, Comdata iConnectData, PhilHealth EPRS, FBR IRIS.