Organization is not eligible for the Education plan

What it means

The API answers with HTTP 403 Forbidden and the application/problem+json document below when the condition is Organization is not eligible for the Education plan. The document's type member is https://screenrig.ai/problems/education-not-eligible, the address of this page, and its code member is education_not_eligible.

What to do

Staff mark verified K-12 schools and districts as eligible. Ask support to verify the organization, or choose the Plus or Premium plan.

Should you retry?

The retryable member appears only on HTTP 5xx problems, so this one has none. Follow the steps under What to do before sending the request again.

Example response

Most routes answer with the error in the first entry of errors, and the document members instance and request_id beside it. The type, code, title and status of this problem type are fixed; detail varies per request, and hint is the registry default unless the handler sets a more specific one.

HTTP/1.1 403 Forbidden
Content-Type: application/problem+json

{
  "errors": [
    {
      "status": 403,
      "code": "education_not_eligible",
      "type": "https://screenrig.ai/problems/education-not-eligible",
      "title": "Organization is not eligible for the Education plan",
      "detail": "What went wrong in this request.",
      "hint": "Staff mark verified K-12 schools and districts as eligible. Ask support to verify the organization, or choose the Plus or Premium plan."
    }
  ],
  "instance": "INSTANCE",
  "request_id": "REQUEST_ID",
  "server_time": "2026-01-01T00:00:00Z"
}

In the API contract

The OpenAPI contract describes this problem in these words:

The app finishes the transaction after a 2xx or a definitive 4xx problem. Problems: app_store_transaction_invalid (422), app_store_account_mismatch (409), education_not_eligible (403), app_store_plan_conflict (409), billed_by_reseller (409, the organization is delegated to a reseller, which pays for its plan).

Operations that name this problem

These operations name this problem in the API reference:

• Record App Store Transaction POST /api/organizations/{organization_id}/app-store/transactions

Related problems

The contract mentions these problems alongside this one:

• The organization is billed through its reseller billed_by_reseller
• App Store purchase could not be verified app_store_transaction_invalid
• Purchase belongs to another organization app_store_account_mismatch
• Organization already holds a plan app_store_plan_conflict

Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

Reference

All problem typesAPI referenceproblems YAML