Request headers
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.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.
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.FormManage).
Request parameters
Form layout mode. Determines where and how the form is used.Possible values:
Custom— user custom fieldsForm— a fillable form (questionnaire)Signup— sign-up form (one per school)Welcome— welcome form (one per school)Participant— product participant form
Internal layout name. Up to 255 characters. Used to identify the layout in the management interface.
Symbolic code of the layout. From 1 to 50 characters. Must be unique within the seller (school).
An array of IDs of products the layout is bound to — the
productId field from the
course list.For the
Signup and Welcome modes, only one layout per seller (school) is allowed. Attempting to create a second layout with the same mode returns the LayoutWithModeAlreadyExists error.Permission requirements
Creating a form layout requires the service user to have the “Forms management” permission (
FormManage).Updated: 2026-09-25 14:33 UTC