Link license to account

Link license to account attaches a license to the current account authorization context. This operation is available only after successful Initialize.

Request

Link license to account uses packet type = 4.

{
  "type": 4,
  "id": 5,
  "license": "ABCDEF-123456"
}

Prop

Type

Response

{
  "id": 5,
  "status": 1
}

Prop

Type

Behavior notes

Operation requires an already authorized account session context.
On success, license is linked to the authorized account and activated.

Link-license statuses

Status	Constant	Returned when
`1`	`Ok`	License was linked successfully.
`3`	`NotAuthorized`	Session is not authorized by account credentials.
`6`	`InternalServerError`	Server failed to process linking due to an internal error.
`100`	`LicenseNotFound`	License was not found in this application.
`101`	`LicenseTooShort`	`license` is shorter than 6 characters.
`102`	`LicenseTooLong`	`license` is longer than 64 characters.
`106`	`LicenseAlreadyLinked`	License is already linked to an account.
`107`	`LicenseAlreadyActivated`	License is already activated.

Connection-close cases (before/around this usecase)

Link license to account itself returns JSON responses with status, but session can still be closed by protocol/session guards:

Close code	Error	When it happens
`4200`	`connection is not initialized`	Request was sent before successful `Initialize`.
`4201`	`rate limit hit`	Global per-session packet rate limit was exceeded.
`4302`	`invalid request body`	Packet body does not match the required schema for this operation.