Skip to content

Empty Secret Value

URI: https://docs.ankatech.co/errors/empty-secret-value
HTTP Status: 400 Bad Request

When you see this

A writable-secret platform setting was submitted with a null, empty or whitespace-only value. Sealing an empty plaintext would produce an envelope that every consumer-side resolve then treats as a failure — a permanently unresolvable secret — so the write is rejected before any seal and before any settings-change notification. The prior ciphertext is left exactly as it was.

Common Causes

  • The console or client sent the field with an empty string after a form was cleared.
  • The value member was omitted from the PUT body entirely.
  • The submitted value contained only whitespace.

Response Example

{
  "type": "https://docs.ankatech.co/errors/empty-secret-value",
  "title": "Empty Secret Value",
  "status": 400,
  "detail": "The submitted secret value must not be empty",
  "instance": "/api/v3/admin/platform/settings/ankasecure.notification.email.sendgrid.api-key",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "f0417ac2-3e69-4b58-92d7-08c6b1e34d5a"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Submit a non-empty value for the setting.
  2. If your intent was to remove the secret rather than change it, use the dedicated clear operation for the setting — this endpoint only sets a non-empty value.
  3. The previously stored value is untouched by the refusal, so the setting continues to resolve as it did before.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.