A new secret key for your tenant (at most 4; revoke_others rotates)
With `revoke_others` the new key is the only one: every other key, the one this call was made with included, stops at once, and so does every console session opened with one. The key is shown once. The default tenant's keys are the environment's (409 `default_tenant`).
With revoke_others the new key is the only one: every other key,
the one this call was made with included, stops at once, and so does
every console session opened with one. The key is shown once. The
default tenant's keys are the environment's (409 default_tenant).
secretKeyAuthorizationBearer <token>sk_...
application/json- body
revoke_others?booleanfalsethe key, once
application/json- response
secret_key?stringshown once; only its SHA-256 is kept
hint?stringits first characters, as GET /v1/tenant lists them
created_at?stringdate-timecurl -X POST 'https://api.nearglass.com/v1/tenant/secret-keys' \ -H 'Content-Type: application/json' \ -d '{ "revoke_others": false}'{ "secret_key": "string", "hint": "string", "created_at": "2019-08-24T14:15:22Z"}The stream's LL-HLS, for a held seat GET
Served from the origin's LL-HLS packager (fed by the gateway from the same ingest) and metered per seat beside the relay's MoQ sessions (`hls` in Usage). Answered only while the seat is held; LL-HLS delivery directives (_HLS_msn, _HLS_part, _HLS_skip) pass through. Only streams with encoder ingest (a stream key) have LL-HLS.
A new publishable key for your tenant (at most 4; revoke_others rotates) POST
Publishable keys are public by design (pages carry them) and are listed in `GET /v1/tenant`. With `revoke_others` the new key is the only one: pages with an old key are refused new seats (401), and seats already held keep working (a seat id is its own bearer). The default tenant's keys are the environment's (409 `default_tenant`).