eLearn Partner API Overview

Audience: developers building an integration against the Master Teacher platform.

The eLearn Partner API is a read-only JSON API for retrieving completed assessments — which assessments an educator has completed, when, and who proctored them.

Base path

https://api.masterteacher.net/api/v1/ax

Your platform host is issued with your credentials — it isn’t the same host as this help site. All endpoints live under the /api/v1/ax path.

What the API gives you

One resource, with two endpoints:

Method	Path	Returns
GET	/api/v1/ax/assessments	A filtered, paginated list of completed assessments
GET	/api/v1/ax/assessments/:id	A single completed assessment

Each record is one educator’s completed assessment, so an educator who has completed three assessments appears three times.

Full details in Assessments.

How access is scoped

Access is provisioned per partner, not per user. An integration is a record on the Master Teacher side that ties your OAuth credentials to:

• a fixed set of organizations (the districts or agencies whose data you may read), and
• a fixed set of assessments (the assessments you may read results for).

Every request is filtered to that intersection automatically. You cannot widen it with a query parameter, and data outside it is simply absent from responses rather than returning an error — so if a result set looks short, the scope of your integration is the first thing to check.

To have an integration provisioned, or to change which organizations or assessments it covers, contact Master Teacher support at support@masterteacher.com.

Conventions

• Format. All responses are JSON. The API sets the response format itself, so an Accept header isn’t required.
• Authentication. OAuth 2.0 client credentials on every request. See Authentication.
• Read-only. Only GET is supported. Nothing in this API creates or changes data.
• Dates. certified_on is a calendar date (YYYY-MM-DD). Date filters accept the same format and are inclusive of the whole day.
• Pagination. List responses carry a meta object with the total matching count. Read the paging parameters before writing a paging loop — the parameter names are not what you’d guess.

Quick start

Request a token, then call the endpoint with it:

# 1. Get an access token (valid for 2 hours)
curl -X POST https://api.masterteacher.net/oauth/token \
  -d grant_type=client_credentials \
  -d client_id=YOUR_CLIENT_ID \
  -d client_secret=YOUR_CLIENT_SECRET

# 2. Call the API with it
curl https://api.masterteacher.net/api/v1/ax/assessments \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

A successful response looks like this, trimmed to one record:

{
  "data": [
    {
      "id": 88212,
      "seid": "1234567",
      "name": "Dana Whitfield",
      "first_name": "Dana",
      "last_name": "Whitfield",
      "email": "dana.whitfield@example.org",
      "organization_id": 412,
      "organization_name": "Riverbend Unified School District",
      "assessment_name": "Classroom Management Assessment",
      "certified_on": "2026-04-18",
      "results": [
        {
          "assessment_id": 88213,
          "assessment_name": "Classroom Management — Part 1",
          "certified_on": "2026-03-02",
          "proctor_id": 5501,
          "proctor_name": "Alex Romero"
        }
      ]
    }
  ],
  "meta": { "count": 1, "offset": 0, "page": 50 }
}

Handling educator data

Responses include personally identifiable information: full name, email address, and State Educator ID. Treat the payload as confidential educator data — keep credentials and responses server-side, and apply whatever retention and disclosure rules govern your use of it.

What isn’t included

The ax API covers completed assessments only. It has no endpoints for:

• assessment or course catalogue data,
• enrollments, attempts, or item-level responses,
• numeric scores or item-level results,
• observations, coaching, or any weCLIMB data,
• creating or updating anything.

If you need something on this list, raise it with Master Teacher support rather than assuming an undocumented endpoint exists.