DELETE /experience-connections/{experienceConnectionId}

Delete an Experience Connection

Deletes the Experience Connection record. Valid from any state.

Standards note. Returns 204 No Content, which by the Alianza Enterprise API Design Standard implies a hard delete (immediate, no recovery). The spec does not state this explicitly.

Spec gap. All Experience Assignments referencing this connection must be deleted before the connection itself can be deleted, but the spec does not state this in the operation description — the rule is only visible via the 409 response. Order your teardown as: delete assignments → delete connection.

Gap ID 4ae891ffc134

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