Application Name Conflict

URI: https://docs.ankatech.co/errors/application-name-conflict
HTTP Status: 409 Conflict

When you see this

A live application of the tenant already uses the requested name. Names are compared without regard to case, so Payments-Gateway and payments-gateway are the same name. Nothing was stored.

Common Causes

POST /api/v3/admin/tenants/{tenantId}/applications named an application that already exists in the tenant.
PATCH /api/v3/admin/tenants/{tenantId}/applications/{applicationId} renamed an application onto the name of another live application.
Two requests claimed the same name at once. The one that lost is refused the same way.

A deleted application does not hold its name.

Response Example

{
  "type": "https://docs.ankatech.co/errors/application-name-conflict",
  "title": "Application Name Conflict",
  "status": 409,
  "detail": "A live application of this tenant already uses this name. Choose another name.",
  "instance": "/api/v3/admin/tenants/7b9c2d10-4e6f-4a21-9c33-0d1e5f7a8b42/applications",
  "timestamp": 1790690531,
  "extensions": {
    "requestId": "2a7f4c91-6e3b-4d58-9f02-b8c1e5d7a364"
  }
}

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

How to Resolve

Choose another name.
Or delete the application that holds the name; a deleted application releases it.

Retrying the same name does not help. The update operation has other 409s that ask for something else: concurrent-modification when another write landed first, and terminal-application-state when a DISABLED application was asked to change status. Branch on type; title is a human label and is not a classifier.

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