Skip to content

Invalid Transport Configuration

URI: https://docs.ankatech.co/errors/invalid-transport-config
HTTP Status: 400 Bad Request

When you see this

A SIEM/XDR forwarding-destination request was refused because of the transport component of the body. The type is deliberately scoped: it is emitted only when every offending field sits under transport, or when the body could not be deserialized along a path that traverses the transport node. An unrelated malformed field — a bad name or formatter — keeps the generic validation 400 instead, so this type always means "the transport shape is wrong for the sink you selected".

Common Causes

  • A field required by the selected sink is missing, blank, or violates its constraint. The detail names the field path and the constraint message.
  • An unknown transport parameter for the selected sink. The parameter name is echoed; the submitted value never is.
  • The legacy key url where the current contract expects endpoint.
  • A transport sub-shape that does not match the declared sinkType — the transport node is a sealed set of per-sink shapes selected by that discriminator, and unknown keys are rejected strictly.

Response Example

{
  "type": "https://docs.ankatech.co/errors/invalid-transport-config",
  "title": "Invalid Transport Configuration",
  "status": 400,
  "detail": "Invalid transport configuration for the selected sink: 'transport.endpoint' must not be blank;",
  "instance": "/api/v3/admin/platform/event-forwarding/destinations",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

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

How to Resolve

  1. Read the detail: it names the offending field path and the constraint that failed, or the unknown parameter name. It never echoes what you submitted.
  2. Check the transport shape against the sink you declared in sinkType — each sink has its own required parameters and rejects keys that belong to another.
  3. Replace a legacy url key with endpoint, then re-submit.

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