---
title: "Why does Create WCP API Client return 409 for an ISU?"
description: "HTTP 409 means that ISU name already has an API client on the Developer Site. Delete the stale client, then create again from App Manager."
url: https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client
---

# Why does Create WCP API Client return 409 for an ISU?

Create API Client 409 means a leftover Developer Site client still uses that ISU name. Delete the stale client (Company Administrator), create again from App Manager, and authorize the tenant.

-   **Checked** against Workday on November 17
-   Applies to **Workday App Manager ISU API clients**
-   2 min read
-   Published November 17
-   By Kiweely

**Create API Client** in App Manager returns **409** with **The name of this ISU is already associated with an API Client** when the Developer Site still has a client registered for that ISU name. App Manager no longer shows the link—often because the ISU was removed and added again—but the Console row remains.

## What Workday creates

When Create API Client succeeds, Workday generates a client named in the form `App: Env: Tenant: ISU: …`. You can then adjust scopes on the Console’s API Clients page. Simplified ISU setup uses that App Manager–created client. Workday notes you cannot reuse legacy WCPISU clients for simplified ISU.

## Fix steps

1.  Sign in to the Developer Site Console with a user who has **Company Administrator** access.
2.  Open **API Clients** (All Clients) and search for the app, environment, tenant, and ISU name.
3.  Confirm you have the row for **this** tenant. Leave clients for other environments of the same app alone.
4.  Delete only the stale client for the ISU you are fixing.
5.  In the tenant, open App Manager → the app → Integration System Users → **Create API Client** again. Confirm and OK.
6.  Authorize the tenant on the new client in the Console, set scopes if needed, then rerun the orchestration or page that needs the ISU.

## Prevent the next 409

| Practice | Why |
| --- | --- |
| Do not remove and re-add an ISU to “refresh” tokens | Breaks the App Manager link without deleting the Console client |
| When you must remove an ISU, delete its Console client in the same change | Avoids orphan clients |
| Keep a record of which client belongs to which tenant | Prevents deleting the wrong environment’s row |
| Treat API client creation as part of every tenant promotion | Matches Assign Integration System Users to an App |

If Create API Client succeeds but orchestrations still say the ISU is not configured, finish orchestration credentials and confirm the username matches. If WQL then returns S22, fix domains next—not the client.

Kiweely Vine can walk you through the App Manager sequence on a developer tenant with consent. Deleting Console clients requires a Developer Site administrator.

## Frequently asked questions

### What is the exact 409 status message?

The name of this ISU is already associated with an API Client. Please contact your Developer Support Contact with the full text of this message for further instructions.

### Who can delete the leftover API client?

Workday’s ISU authentication concept lists Company Administrator access on the Developer Site for deleting API clients associated with deleted ISUs.

### Should I remove and re-add the ISU to fix token errors?

Avoid that pattern. It drops the App Manager link while leaving the Console client, which is how you get 409 on the next Create API Client.

## Sources checked

-   [Assign Integration System Users to an App](https://developer.workday.com/documentation/GUID-72d57df4-c4ec-4825-a6e8-fdd596cf930e/AssignIntegrationSystemUserstoanApp)
-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus/ConceptISUAuthentication)
-   [Steps: Set Up ISU Authentication for Apps](https://developer.workday.com/documentation/GUID-3277fec3-24c9-41da-9840-c61b41033f28-enHYPHENus/StepsSetUpISUAuthenticationforApps)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How do I fix “WCPISU is not configured” on an Extend orchestration? WCPISU is not configured means the ISU is missing from App Manager or has no API client. Assign the ISU, create the client, then finish orchestration credentials. Prefer simplified ISU for new apps.](https://kiweely.com/guides/workday-extend-wcpisu-not-configured-error)
-   [### WCPISU explained: the legacy Workday Cloud Platform integration system user in Extend WCPISU is Extend’s legacy way for a page endpoint to run as an integration system user: you get a refresh token for the ISU, store it with Create External Client CredStore, and point the SMD at it by appId and tokenHolder. New apps must use the simplified ISU scheme instead.](https://kiweely.com/guides/workday-wcpisu-explained)
-   [### Workday ISU or API client 401, invalid\_client, invalid\_grant These errors usually blame the token, but the real cause is the ISU’s own account, its security group’s activation, or the wrong client task — not a corrupted credential.](https://kiweely.com/guides/workday-isu-authentication-errors)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [How do I set an Integration System Security Group for an Integration System User?](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)
-   [Why does Object Transporter block single-instance migration from Production?](https://kiweely.com/guides/workday-ox-production-single-instance-limits)
-   [EIB spreadsheet mapping when an AI assistant drafts the load](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [Custom reports and RaaS when an AI assistant is helping you build them](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [Mass Action Tables Are Quietly Replacing Routine HR EIBs, Except Where Dirty Source Data Lives](https://kiweely.com/blog/when-mass-action-tables-replace-workday-eibs)
-   [Does Workday Data Cloud Kill Outbound RaaS and Studio Extracts? A Consultant’s Reality Check](https://kiweely.com/blog/workday-data-cloud-live-data-query-for-consultants)
-   [I Used to Spend My Afternoon on One EIB File. Now I Hand It to Kiweely.](https://kiweely.com/blog/messy-spreadsheet-eib)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
