Secrets
Integrator-facing notes on Runtime-related secret classes and safe handling. Never publish live credentials or private keys in docs examples.
Other secret families (signing material, Host/platform.json, and similar) remain thin stubs until dedicated pages expand them.
License keys (Runtime AuthN)
A human license key (XXXX-XXXX-XXXX-XXXX v1 or XXXX-XXXX-XXXX-XXXX-XXXX v2) is a customer/integration secret used when a product calls the Runtime plane (typically via official SDKs: optional LicenseKey / MYHORECA_LICENSE_KEY). See License Keys.
| Do | Don't |
|---|---|
| Store in a secret manager or operator vault | Commit real keys into source control or docs samples |
| Prefer SDK typed options / env vars | Log the full key (use public prefix / mask only) |
| Rotate in Management after compromise | Treat Compact JWS leases (MH-LEASE-V1, …) as the same credential |
Format, normalize rules, and storage: License Keys.
Validate / activate flows: API Reference · SDKs.
Management issue/rotate HTTP APIs are not published on this public site.
Next steps
- License Keys
- SDK matrix (env var notes)
- Start here: Getting Started
- Vocabulary: Core Concepts
- Integrator APIs: API Reference
- Errors: Error catalog