Skip to main content

Request headers

string
required
The service user’s API token in the Bearer YOUR_TOKEN format. The school owner issues the token in the admin panel: Manage → School → For developers → API keys — see the “Authentication” section for details.
integer
required
The numeric ID of the seller — the account the school belongs to. Copy it on the API keys page, in the Integration data → Identifiers card. The token’s permissions are checked against this ID.
integer
required
The numeric ID of the school, found in the same place as Seller-Id. The value must match the seller’s school — otherwise a 400 error with cause: "ForbiddenSchoolMismatch" is returned.
Requires authentication and the “School User Management” permission (SchoolManageUsers).
To find a single user, use Find by identifier.

Request parameters

Pass at least one of the identifier lists
The method returns an array of found users. Users that could not be found are not included in the response — match the result to the request by email/phone/domain/tgId/extId on your side. If several lists are passed, the conditions are combined with “OR”: the response includes every user matching at least one value from any list — each user at most once. The order of items in the response does not match the order in the request.
string[]
A list of user logins: email, phone in international format, or domain login (domain, for example i_ivanov; a value like id12345 finds the user with ID 12345). From 2 to 50 characters each, up to 250 items.
integer[]
A list of users’ Telegram IDs. Up to 250 items.
string[]
A list of external identifiers from your system. From 1 to 50 characters each, up to 250 items.
You must pass at least one non-empty list. Each list is limited to 250 items.

Permission requirements

Finding users requires the “School User Management” permission (SchoolManageUsers).
The service user must be authenticated with a token and have the appropriate access permissions for the specified school.

Updated: 2026-09-25 14:33 UTC