Pull your Slate Reader and checklists into your systems

What you can build on Slate

• Get the records in a Reader bin

  Build this

  Opens Search in Reader, filters by the bin you name and reads the list of records in that stage of the workflow.

  Takes

  Bin name, workflow (optional)

  Returns

  Record name, bin, queue assigned to, count of records

• Check an application's checklist

  Build this

  Opens one application record and reads its checklist: each item's Details, Status and Date, including Received Copy and Hidden items staff can see.

  Takes

  Applicant name or Slate ID

  Returns

  Item name, status (Received, Awaiting, Waived, Received Copy, Hidden), date

• Get your Reader queue

  Build this

  Opens Queue in Reader and reads the records currently assigned to your account for review.

  Takes

  Nothing

  Returns

  Record name, bin, count of records

• Move a record to another bin

  Build this

  Opens a record in Reader, uses Edit Bin/Queue to place it in the bin you name and confirms the change.

  Takes

  Applicant name or Slate ID, bin name

  Returns

  Record name, previous bin, new bin

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

• Applications in Awaiting Materials, every weekday morning

  Build this

  Starts

  Every weekday at 7:30

  Step 1

  Get the records in the Awaiting Materials bin.

  Step 2

  For each record, check the application's checklist.

  Step 3

  Keep the items with status Awaiting.

  Step 4

  Email you the list, one line per applicant with the missing items.

• Weekly count of records in each review bin

  Build this

  Starts

  Every Monday at 8:00

  Step 1

  For each bin you name, get the records in that Reader bin.

  Step 2

  Compare the counts with last week's run.

  Step 3

  Post bin, count and change since last week to your webhook.

• Newly received checklist items for your queue

  Build this

  Starts

  Every day at 16:00

  Step 1

  Get your Reader queue.

  Step 2

  For each record, check the application's checklist.

  Step 3

  Keep the items marked Received that were not Received on the last run.

  Step 4

  Email you each applicant with the items that arrived.

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 the records in a Reader bin” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "apply.example.edu/get_reader_bin_records",
    "input": {
      "bin": "Ready for Decision"
    }
  }'

{
  "status": "completed",
  "data": {
    "bin": "Ready for Decision",
    "records": [
      {
        "name": "Jordan Acme",
        "bin": "Ready for Decision",
        "queue": null
      }
    ],
    "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.

Slate’s own options

Slate's way out for data is its queries. A user with the Administrator (All Access) role can turn any Configurable Joins query into a web service returning JSON, XML, Excel or CSV, or schedule it to push data to a remote web service or SFTP server. Without such a query, staff work in Reader and on records by hand.

Read on November 12, 2026: Exporting data with web services, User accounts, Reader overview.

Signing in to Slate

Staff usually sign in to Slate through their institution's single sign-on, with whatever second step the campus adds. External users sign in at the External Login URL with a Slate password, and Slate's own MFA texts a code on an unrecognized browser. With Fous you sign in once through that sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

Your permissions decide what a method sees

Population permissions limit which records each user can open, and realms limit objects further. A method reads only the bins, records and checklists your account can.

Web services need an administrator

Only a user with the Administrator (All Access) role can grant Web Service access to a query, and each database is limited to 300 requests and 300 seconds of web service time in any 5 minutes.

Staff see checklist statuses applicants do not

Applicants see Received, Awaiting and Waived. Staff also see Received Copy, shown to applicants as Received, and Hidden items, which applicants never see.

Bins come from your workflows

Bin names such as New, In Progress or Ready for Decision are set in each Workflow, so a method takes the bin name your office uses as an input.

More in Education, research and nonprofit

• 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
• UCAS adviser portal
• Benevity Causes Portal

Other industries: British Gas Business online account, SGWS Proof, Banno Business, U.S. Bank Access Online, 登記情報提供サービス, MCA21.