Get your Arbor MIS registers and reports as JSON

What you can build on Arbor

• Get incomplete registers

  Build this

  Reads Students > Attendance > Incomplete registers for a date range, including the Unopened tab, with each register's Marks counts.

  Takes

  Date range (optional), unopened only (optional)

  Returns

  Register, date, present, late, absent, students without a mark, unopened

• Get persistent absentees

  Build this

  Reads Students > Attendance > Absentees > Persistent Absentees with the dates and minimum absence percentage you choose.

  Takes

  Date range, minimum absence percentage, exclude leavers (optional)

  Returns

  Student, form, unauthorised absence %, authorised absence %, present %

• Run a report from the Report Library

  Build this

  Opens a custom report by name from Reporting > Report Library, fills in its parameter if it asks for one, and reads the rows.

  Takes

  Report name, parameter (optional)

  Returns

  Report name, column names, rows

• List pending partner app requests

  Build this

  Reads System > Partner Apps (API Users) > Pending requests and, for each app, the Read, Write, Update and Delete permissions it asks for.

  Takes

  Nothing

  Returns

  App, requested read, write, update and delete permissions

Automate Arbor 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.

• Registers still incomplete after morning registration

  Build this

  Starts

  Every weekday at 9:30, Europe/London

  Step 1

  Get today's incomplete registers, including the unopened ones.

  Step 2

  Stop the run when there are none.

  Step 3

  Email you the list with each register's unmarked count and whether it was opened.

• New persistent absentees, posted to your own system

  Build this

  Starts

  Every Monday at 7:00, Europe/London

  Step 1

  Get the persistent absentees for this academic year at 10% absence or more.

  Step 2

  Keep the students who were not on the list last week.

  Step 3

  Post each one, with form and absence percentages, to your webhook.

• Partner app requests waiting for approval

  Build this

  Starts

  Every weekday at 8:00, Europe/London

  Step 1

  List the pending partner app requests.

  Step 2

  Keep the requests that were not there on the last run.

  Step 3

  Email you each app with the permissions it asks for.

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 incomplete registers” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "login.arbor.sc/get_incomplete_registers",
    "input": {
      "from": "2026-11-12",
      "to": "2026-11-12"
    }
  }'

{
  "status": "completed",
  "data": {
    "registers": [
      {
        "register": "Year 8 Form 8N, AM",
        "date": "2026-11-12",
        "present": 24,
        "late": 2,
        "absent": 1,
        "without_mark": 3,
        "unopened": false
      }
    ],
    "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.

Arbor’s own options

Arbor offers REST and GraphQL APIs, with developer documentation and SDKs, to integration partners who build on its network of schools. Partners set up integrations through Arbor's Developer Portal, and each school then approves the app and its permissions in the MIS. School staff work in Arbor itself, where lists such as Persistent Absentees have a Download button.

Read on November 12, 2026: Become a Partner, Setting up integrations FAQ, Setting up and managing third-party API integrations in Arbor.

Signing in to Arbor

Staff sign in to Arbor with their email address and password, and the sign-in page has a Change school button. MAT staff sign in to the MAT MIS, and Arbor logs you out after two hours of inactivity. With Fous you sign in once through Arbor's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Registers appear 10 minutes after the start

A register shows in Incomplete registers 10 minutes after the class's scheduled start time, and registers nobody has opened are on the Unopened tab. Schedule a morning check after registration has closed.

Reports follow the account

In the Report Library, a regular user sees only the custom reports they created or that were shared with them. A method that runs a report needs an account that can see it.

Approving apps needs an admin permission

Approving a partner app needs the School: User Accounts: Administer permission on each school site. MAT staff need User Details: Manage All Users and approve in each school's MIS, reached from the MAT MIS.

Integrations wait until the site is live

Arbor sets up third-party API integrations only once a school's site is live, so a school whose Arbor site is not live yet cannot approve one.

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
• SLC HEP Services
• Parchment
• UCAS adviser portal
• Benevity Causes Portal

Other industries: Duke Energy My Account, Just Eat Partner Hub, DBS IDEAL, Paymode-X, 全国统一规范电子税务局, Income Tax e-Filing Portal.