Get your UCAS adviser portal data through an API

What you can build on the adviser portal

• Get applicant statuses

  Build this

  Reads the applicant list in Application management: each student's Applicant status, group and section progress, filtered by status or group.

  Takes

  Applicant status (optional), group (optional)

  Returns

  Name, Personal ID, group, applicant status, sections not yet complete

• Track offers and decisions

  Build this

  Reads Tracking offers and decisions for your applicants: each choice with its decision, the applicant's reply and the Last updated date.

  Takes

  Updated since (optional), group (optional)

  Returns

  Name, Personal ID, group, university or college, course, decision, offer conditions, reply, last updated

• Read the Applicant Status Report

  Build this

  Downloads the Applicant Status Report from the adviser portal and returns its rows: choices, offers in full and predicted grades for each applicant.

  Takes

  Group (optional)

  Returns

  Personal ID, name, group, choices, offer codes, full conditions, replies, predicted grades

• Add predicted grades and save a reference

  Build this

  Opens one applicant's application in Application management, enters predicted grades and the reference text and saves them, without approving or sending.

  Takes

  Personal ID, predicted grades by qualification, reference text

  Returns

  Personal ID, predicted grades saved, reference status

Automate the adviser portal 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 offers and decisions, posted to your MIS

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Track offers and decisions for all your applicants.

  Step 2

  Keep the decisions and replies that changed since the last run.

  Step 3

  Post each one, with Personal ID, choice, decision and conditions, to your MIS webhook.

• Weekly section progress, by group

  Build this

  Starts

  Every Monday at 7:30

  Step 1

  Get applicant statuses and section progress from Application management.

  Step 2

  Keep the applicants with sections still incomplete.

  Step 3

  Email you the list, one section per group, with the sections each student has left.

• Applicant Status Report snapshot to your data warehouse

  Build this

  Starts

  Every Friday at 17:00

  Step 1

  Read the Applicant Status Report for all applicants.

  Step 2

  Post every row, with choices, offer codes and predicted grades, to your warehouse webhook.

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 “Get applicant statuses” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "digital.ucas.com/get_applicant_statuses",
    "input": {
      "group": "13B"
    }
  }'

{
  "status": "completed",
  "data": {
    "group": "13B",
    "applicants": [
      {
        "name": "Sam Acme",
        "personal_id": "100-000-0001",
        "group": "13B",
        "applicant_status": "Ready to send to university / college",
        "sections_not_complete": []
      }
    ],
    "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.

The adviser portal’s own options

UCAS's Adviser Guide and adviser portal terms describe no API or data feed for centres. In the adviser portal you can follow Tracking offers and decisions and download the Applicant Status Report and Final Destination Report as an Excel spreadsheet. UCAS also sells Adviser Reports packages per centre and cycle.

Read on November 12, 2026: UCAS Adviser Guide 2027, Monitor, report and showcase your students' progression, Adviser portal terms of service.

Signing in to the adviser portal

Each member of staff signs in to the adviser portal with their own username and password, registered with an email address on the centre's own domain, and UCAS uses multi-factor authentication for all users. With Fous you sign in through UCAS's own sign-in with your own account, and the login is sealed with AES-256, never returned by the API or written to logs.

Worth knowing

Tracking is restricted during embargoes

Access to Tracking offers and decisions is restricted during embargo periods. UCAS advises downloading what you need, such as the Applicant Status Report, before they start.

Two approvals before an application is sent

Both the application and its reference must be approved by the centre before it goes to UCAS. Once the centre has sent it, the application cannot be returned to the student.

Each user sees what their permissions allow

Staff, permissions, referees, groups and the qualifications shortlist roll over each cycle. A user's Applicant Status Report only lists the applicants their permissions show, so run methods from an account that sees the whole cohort.

Offer codes in the reports

The Applicant Status Report uses codes such as C(CF) for a conditional offer firmly accepted, UI for an unconditional insurance offer, REJ for unsuccessful and W for withdrawn.

More in Education, research and nonprofit

• Slate
• Naviance
• Common App for Recommenders
• National Student Clearinghouse secure site
• AQA Centre Services
• 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
• Benevity Causes Portal

Other industries: Georgia Power My Account, Swiggy Partner, Itaú Empresas, Synchrony Business Center, MyTax, FBR IRIS.