Using Management API
Follow proven architectural design patterns for managing fleet credentials, monitoring monthly API spend, and meeting corporate compliance requirements.
Getting started with Management keys
Management keys have full administrative control over your Plannix organization. Ensure they are stored securely in dedicated secrets vaults and never checked into Git.
Automated rotation design pattern
Use zero-downtime rotation: create a secondary key, verify its propagation across our global edge caches, update deployment environment variables, and delete the prior key.
# 1. Create secondary key
NEW_KEY=$(curl -X POST https://management-api.plannix.web.id/v1/mgmt/auth/keys \
-H "Authorization: Bearer ${MGMT_KEY}" \
-d '{"name": "prod-runner-v2"}' | jq -r .key)
# 2. Check propagation status
curl https://management-api.plannix.web.id/v1/mgmt/auth/keys/prod-runner-v2/propagationAutomated budget alerts
Query GET /v1/mgmt/billing/usage from a daily Lambda function to detect spend anomalies before exceeding organizational allocations.
Continuous SIEM log extraction
Poll GET /v1/mgmt/audit/events incrementally to synchronize audit trails into Datadog, Splunk, or cloud object storage.