Upload a new license. The license must be a valid Ed25519-signed license string
POST /api/license
Auto-generated from server.go. Handler: s.UploadLicense.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Request body for POST /api/license. The license field carries the
full Ed25519-signed license document as a single string (PEM-like
envelope, base64 payload). Server verifies signature before accepting.
object
Ed25519-signed license document (the full file contents).
Responses
Section titled “ Responses ”Successful response
Returned by POST /api/license after a license is verified, parsed, and
persisted. Echoes the parsed license payload so the caller can show the
new state without a follow-up GET /api/license.
object
Always true on the 200 path; lets callers branch on success rather than HTTP status.
Issuer-assigned identifier on the new license.
License tier marketing name.
ISO-8601 calendar date as a plain string (YYYY-MM-DD).
ISO-8601 calendar date as a plain string (YYYY-MM-DD).
The request body or parameters failed validation.
Standardised error envelope per RFC 7807. Many existing endpoints still
return an older shape (e.g. {"error": "..."}). This schema documents the
target shape; legacy endpoints will be migrated in Phase 70. Per D-21 the
spec describes current behaviour without enforcing the migration here.
object
A URI reference that identifies the problem type.
A short human-readable summary of the problem.
The HTTP status code generated by the origin server.
A human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.
Legacy error message field. Will be removed once handlers are migrated.
Legacy per-field error details. Will be removed once handlers are migrated.
object
The request id middleware-assigned identifier for tracing.
Authentication is required or the supplied token is invalid.
Standardised error envelope per RFC 7807. Many existing endpoints still
return an older shape (e.g. {"error": "..."}). This schema documents the
target shape; legacy endpoints will be migrated in Phase 70. Per D-21 the
spec describes current behaviour without enforcing the migration here.
object
A URI reference that identifies the problem type.
A short human-readable summary of the problem.
The HTTP status code generated by the origin server.
A human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.
Legacy error message field. Will be removed once handlers are migrated.
Legacy per-field error details. Will be removed once handlers are migrated.
object
The request id middleware-assigned identifier for tracing.
Internal server error
Standardised error envelope per RFC 7807. Many existing endpoints still
return an older shape (e.g. {"error": "..."}). This schema documents the
target shape; legacy endpoints will be migrated in Phase 70. Per D-21 the
spec describes current behaviour without enforcing the migration here.
object
A URI reference that identifies the problem type.
A short human-readable summary of the problem.
The HTTP status code generated by the origin server.
A human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.
Legacy error message field. Will be removed once handlers are migrated.
Legacy per-field error details. Will be removed once handlers are migrated.
object
The request id middleware-assigned identifier for tracing.