DELETE /experience/connections/{experienceConnectionId}

Delete an Experience Connection

Deletes the Experience Connection record. Valid from any state.

Deletion is permanent. Returns 204 No Content. The delete is a hard delete — immediate, with no recovery and no soft-deleted state to restore from. The spec does not state this explicitly, so confirm with Alianza before relying on it in a destructive flow.

Delete assignments first. A connection cannot be deleted while Experience Assignments still reference it — that is what the 409 below means. Order your teardown as: delete assignments → delete connection.

Authentication

OAuth 2.0. Required scope(s): experience-connections:manage.

Request

Path parameters

Query parameters

None.

Headers

None.

Responses

204 — Experience Connection deleted successfully

401 — Unauthorized - Missing or expired access token. Obtain a new token and retry.

Content-Type: application/problem+json

Schema: ProblemDetails

Example:

{
  "title": "Unauthorized",
  "status": 401,
  "detail": "Access token is missing or has expired",
  "traceId": "6d4a3a62-0d4b-4b96-9171-8c5070e01c35"
}

403 — Forbidden - Experience Connection exists, the authenticated user has authorization to read but no authorization to delete the Experience Connection

Content-Type: application/problem+json

Schema: ProblemDetails

Example:

{
  "title": "Forbidden",
  "status": 403,
  "detail": "The authenticated user does not have authorization to delete this Experience Connection",
  "traceId": "6d4a3a62-0d4b-4b96-9171-8c5070e01c35"
}

404 — Not Found - Experience Connection does not exist, already deleted, or the authenticated user does not have authorization to access it

Content-Type: application/problem+json

Schema: ProblemDetails

Example:

{
  "title": "Resource Not Found",
  "status": 404,
  "detail": "The requested Experience Connection does not exist or has already been deleted",
  "traceId": "6d4a3a62-0d4b-4b96-9171-8c5070e01c35"
}

409 — Conflict - Experience Connection cannot be deleted while TNs are still assigned to the Experience

Content-Type: application/problem+json

Schema: ProblemDetails

Example:

{
  "title": "Conflict",
  "status": 409,
  "detail": "The Experience Connection cannot be deleted while TNs are still assigned to the Experience",
  "traceId": "6d4a3a62-0d4b-4b96-9171-8c5070e01c35"
}

Errors

This operation may return:

• 401 — Unauthorized - Missing or expired access token. Obtain a new token and retry.
• 403 — Forbidden - Experience Connection exists, the authenticated user has authorization to read but no authorization to delete the Experience Connection
• 404 — Not Found - Experience Connection does not exist, already deleted, or the authenticated user does not have authorization to access it
• 409 — Conflict - Experience Connection cannot be deleted while TNs are still assigned to the Experience

See Errors reference for the full catalogue.

Related

• Schema: ProblemDetails