Issue another Blinq service secret
Requires platform-administrator authority. Generated from the production route registered in `internal/features/runners/inbound/http.go`. Issues a new nonexpiring secret for an active Blinq service without invalidating earlier secrets. No request body is read. The plaintext is returned once with Cache-Control: no-store; only its hash is stored, in the same transaction as the audit record.
/v1/admin/blinq-services/{id}/secretsRequires platform-administrator authority. Generated from the production route registered in internal/features/runners/inbound/http.go. Issues a new nonexpiring secret for an active Blinq service without invalidating earlier secrets. No request body is read. The plaintext is returned once with Cache-Control: no-store; only its hash is stored, in the same transaction as the audit record.
Engine-issued API key or tenant-signed JWT.
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/admin/blinq-services/497f6eca-6276-4993-bfeb-53cbbbba6f08/secrets"{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "service_id": "641e839f-864e-4cce-98f9-40f6cbb3e9e0", "created_at": "2019-08-24T14:15:22Z", "token": "string"}Revoke a Blinq service
Requires platform-administrator authority. Generated from the production route registered in `internal/features/runners/inbound/http.go`. Revokes the service, all its secrets and every paired server in one audited transaction, including a server pairing at that moment. No future pairing or secret issuance is allowed for the revoked service. Records are retained; this is revocation, not deletion. Repeating the revocation succeeds with no body.
Revoke one Blinq service secret
Requires platform-administrator authority. Generated from the production route registered in `internal/features/runners/inbound/http.go`. Revokes only this service's named secret and unpairs the servers paired through it, in the same audited transaction. Other secrets and their servers keep working. The secret must belong to the service in the path. Repeating the revocation succeeds with no body. Concurrent pairing either commits first and is then unpaired, or is refused after revocation.