Documentation Index
Fetch the complete documentation index at: https://docs.knoxcall.com/llms.txt
Use this file to discover all available pages before exploring further.
POST /admin/tenant-kms
Onboard a customer KMS provider. KnoxCall performs a live wrap + unwrap round-trip on a 32-byte test payload before committing — if the IAM/RBAC grant isn’t working, the request fails immediately and nothing is stored. Calling this endpoint when a KMS configuration already exists replaces it (UPSERT). The probe runs first; if it fails, the existing config is unchanged. Auth:Authorization: Bearer <token> — no step-up required.
Request body
provider — aws | gcp | azure
kms_key_ref — The provider-specific key identifier:
- AWS: full key ARN (
arn:aws:kms:REGION:ACCOUNT:key/KEY-IDor.../alias/ALIAS) - GCP: full resource path (
projects/P/locations/L/keyRings/R/cryptoKeys/K) - Azure: vault key URL (
https://VAULT.vault.azure.net/keys/KEY-NAME)
config — Provider-specific authentication references. Static long-lived credentials (access keys, service account JSON, client secrets) are rejected at the API level.
| Provider | Required | Optional |
|---|---|---|
aws | region, role_arn | external_id |
gcp | impersonate_service_account | project_id |
azure | vault_url | azure_tenant_id, client_id, client_secret_env_var |
Response
rewrap_status is always "enqueued" — KnoxCall unconditionally issues a background rewrap lease after onboarding.