API Key Management
Create and manage secure API keys for the PlatPhorm News Network
Security model
How does PlatPhorm Keys protect a platform credential?
Keys treats issuance as a lifecycle, not a text generator. An authenticated operator requests the smallest useful scopes; the service applies a distributed rate limit, encrypts the durable record with AES-256-GCM, and returns generated secret material once. Later reads expose identifiers, prefixes, scopes, status, and audit evidence—not the original secret. Validation, rotation, and revocation remain protected and traceable.
- 1. Bound issuanceShared platform authentication, tenant-aware policy, allowed scopes, and atomic DynamoDB limits are checked before a credential is created.
- 2. Reveal onceThe generated value is returned only in the successful creation response. Discovery, telemetry, logs, traces, lists, and validation results exclude raw key material.
- 3. Prove lifecyclePublic health shows safe infrastructure state. Protected audit trails and Trace-linked operations provide evidence for validation, rotation, revocation, and delivery failures.
Encryption
AES-256-GCM
Observability
OpenTelemetry
Auto Fingerprint
Enabled
Geo Tracking
Active
Kept only in this page session; never written to browser storage.
API Keys
Public status is read-only. Issuance and lifecycle operations require PLATPHORM_API_KEY.
| Name | Key | Scopes | Status | Created | Last Used | |
|---|---|---|---|---|---|---|
Protected key metadata is locked Enter PLATPHORM_API_KEY above to load it. | ||||||
Protected Key Provisioning
Operator-authenticated and bounded. Generated PLATPHORM_API_KEY secrets are shown only once.