Skip to content

Backend Endpoint Refused

URI: https://docs.ankatech.co/errors/backend-endpoint-refused
HTTP Status: 400 Bad Request

When you see this

The endpoint carried by the submitted key-protection backend coordinates is one this deployment may not dial. The rule is applied again where the decision to open a socket is taken, so the refusal reaches you even on a path that did not pass through the boundary constraint that normally screens the same value. The detail names the rule that refused; the rejected endpoint itself is never echoed back.

Common Causes

  • The value is not a parseable absolute URL, or its scheme is not https.
  • The authority embeds inline user:password@ credentials, or the URL carries no host.
  • The host is a single label, or ends in localhost, .localhost, .internal or .local.
  • The host is an IP literal in an ambiguous notation, or a loopback, link-local, CGNAT or multicast address.
  • The endpoint names a port other than the default HTTPS port. That arm is enforced only where a socket would open, so such a value can be stored and is still refused when the platform tries to dial it.

Response Example

{
  "type": "https://docs.ankatech.co/errors/backend-endpoint-refused",
  "title": "Backend Endpoint Refused",
  "status": 400,
  "detail": "The configured backend endpoint must use the 'https' scheme.",
  "instance": "/api/v3/admin/platform/setup/backend/validate",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "9f2c1b74-3ad8-4e05-b1c6-8e07d3a91f42"
  }
}

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

How to Resolve

  1. Read the detail: it is the refusing rule's own fragment, so it names the property of the endpoint to change.
  2. Replace the endpoint with the vendor-published HTTPS endpoint for the account — no embedded credentials, no explicit port, a routable multi-label host.
  3. Re-submit the coordinates. This type marks a policy refusal, not a malformed body, so do not look for a syntax defect: the value parsed and the rule declined it.

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