---
title: "Register API Client vs. API Client for Integrations"
description: "Compare Workday Register API Client and Register API Client for Integrations: OAuth grant types, PKCE, ISU scope, refresh tokens, and security domain rules."
url: https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations
---

# Register API Client vs. Register API Client for Integrations in Workday

Use Register API Client with Authorization Code Grant and PKCE when external apps act on behalf of a signed-in worker. Reserve Register API Client for Integrations for headless background jobs bound to a single Integration System User.

-   **Checked** against Workday on November 15
-   Applies to **Workday APIs & Security**
-   7 min read
-   Published November 15
-   By Kiweely

Use **Register API Client** when a human signs in to Workday and the external application must inherit that worker’s exact domain, supervisory organization, and row-level security. Reserve **Register API Client for Integrations** strictly for unattended server-to-server pipelines that run under a dedicated Integration System User (ISU).

Choosing the wrong registration task is one of the most common architectural mistakes in Workday API projects. Connecting an interactive portal, reporting add-in, or AI assistant through an integration client forces every query through a single privileged service account—erasing per-worker audit trails and forcing external engineers to rebuild Workday’s security model outside the tenant.

## Architectural Comparison: User-Delegated vs. Integration Clients

Workday separates interactive OAuth 2.0 clients from machine-to-machine OAuth clients across two distinct tasks, two separate tabs on the **View API Clients** report, and two completely different identity models.

| Dimension | Register API Client | Register API Client for Integrations |
| --- | --- | --- |
|  **Workday Task Name** | `Register API Client` | `Register API Client for Integrations` |
|  **View API Clients Tab** |  **API Clients** |  **API Clients for Integrations** |
|  **Runtime Identity** | The individual Workday account that completes browser sign-in | A fixed `Integration System User` (ISU) |
|  **Supported Grant Types** | Authorization Code Grant (with optional PKCE), Implicit Grant, JWT Bearer Grant (for specific data cloud flows) | Refresh Token flow (pre-generated for an ISU) or JWT Bearer Grant (X.509 public certificate) |
|  **User Sign-In & SSO/MFA** | Redirects user to Workday Authorize Endpoint; enforces SAML SSO, OIDC, and MFA policies | Headless; `Do Not Allow UI Sessions` is typically checked on the ISU |
|  **Refresh Token Behavior** | Rotating refresh grant bounded by **Refresh Token Timeout (in days)** from initial sign-in |  **Non-Expiring Refresh Tokens** option or static refresh value generated via `Manage Refresh Tokens for Integrations` |
|  **Row & Org Security** | Contextual (`Employee As Self`, `Manager` constrained to supervisory org, intersection groups) | Static, typically bound to an `Integration System Security Group (Unconstrained)` |
|  **Workday Audit Attribution** | Logged under the individual worker’s `Workday Account` in user activity and business process history | Logged under the shared ISU account name |

Tenant Prerequisite

Neither client type can issue or validate OAuth bearer credentials unless **OAuth 2.0 Clients Enabled** is checked on the **Edit Tenant Setup - Security** task.

## How Register API Client Enforces Per-Worker Security

When you create a client with **Register API Client** and select **Authorization Code Grant** (paired with **Support Proof Key for Code Exchange (PKCE)** for public or hybrid clients), Workday issues two tenant-specific URLs alongside the Client ID:

-   **Authorization Endpoint:** `https://<workday-host>/<tenant>/authorize`
-   **Token Endpoint:** `https://<workday-services-host>/ccx/oauth2/<tenant>/token`

When an employee connects an external application, their browser opens the Authorization Endpoint. Workday evaluates your tenant’s authentication policy—routing the employee through corporate SAML SSO, OpenID Connect, or native MFA—and returns a short-lived authorization code to the registered **Redirection URI**.

Once the application redeems that code at the Token Endpoint, the resulting Bearer access credential carries the identity of that specific worker. Every downstream call to Workday REST APIs, Workday Query Language (`/data`), SOAP web services, or web-service-enabled custom reports (RaaS) evaluates **two** boundaries simultaneously:

1.  **API Client Scope (Functional Areas):** Can this client touch endpoints in `Staffing`, `Absence`, or `Core Compensation` at all?
2.  **Worker Configurable Security:** Does the signed-in worker belong to a security group (`Employee As Self`, `Manager`, `HR Partner`) with View or Modify permissions on the underlying domain or business process security policy for the target worker and organization?

If a line manager queries `/workers` or runs a WQL query with a user-delegated Bearer credential, Workday returns only their direct and subordinate supervisory organization rows. They never see peer managers’ compensation or executive records. Step-by-step configuration details are covered in [How to Configure User-Delegated OAuth 2.0 Authorization Code Grant in Workday](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup).

Works

```
GET /ccx/api/v1/gms/workers/me HTTP/1.1
Host: services1.wd3.workday-host.example
Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6...
Accept: application/json
```

## How Register API Client for Integrations Works

**Register API Client for Integrations** omits interactive browser redirects and authorization codes altogether. Because night-time payroll exports, benefits feeds, and data warehouse syncs have no human sitting at a browser to pass MFA, an administrator binds the client directly to an **Integration System User**.

### Standard Setup Sequence for an Integration Client

1.  Run **Create Integration System User** (secured to the *Integration Security* domain in the *Integration* functional area). Set **Session Timeout Minutes** to `0` and select **Do Not Allow UI Sessions**.
2.  Run **Create Security Group** to create an **Integration System Security Group (Unconstrained)** (ISSG) or constrained equivalent, and add the ISU.
3.  Grant domain permissions (`Get`/`Put` for SOAP integration permissions, or `View`/`Modify` under Report/Task permissions for REST and WQL) and run **Activate Pending Security Policy Changes**.
4.  Run **Register API Client for Integrations**, select the required **Scope (Functional Areas)**, and select **Non-Expiring Refresh Tokens** if the downstream middleware cannot handle periodic manual credential rotation.
5.  Open the client’s related actions menu (**API Client > Manage Refresh Tokens for Integrations**), select the ISU in the **Workday Account** prompt, and generate the refresh value.

At runtime, the integration exchanges that refresh value at the Token Endpoint:

Works

```
POST /ccx/oauth2/gms/token HTTP/1.1
Host: services1.wd3.workday-host.example
Content-Type: application/x-www-form-urlencoded

grant_type=refresh_token&client_id=ODQ4ZDdkNzItMzhiMC00YmFmLTgyNzAtNzljNjM0MDlmNmY2
```

*(Authenticate the POST request with an HTTP Basic header carrying the Base64-encoded Client ID and Client Secret pair, and include the form-encoded `refresh_token` parameter alongside `grant_type=refresh_token`.)*

## Why ISU Clients Fail Security Review for Employee-Facing Tools

Using **Register API Client for Integrations** behind an employee portal, chat bot, or AI tool creates three immediate governance failures:

1.  **Over-privileged blast radius:** Because one ISU serves the entire workforce, its ISSG must hold unconstrained `View` (and often `Modify`) permissions across every supervisory organization in the company. Any bug in external filtering logic or prompt handling exposes another employee’s personal or compensation data.
2.  **Broken business process attribution:** If an integration client submits a `Request Time Off` or `Change Personal Information` transaction, Workday’s **View Worker History** and business process audit trail show the ISU as the initiator—destroying non-repudiation and breaking condition rules that check initiator security groups.
3.  **Sensitive Data Enumeration lockouts:** Workday’s **Sensitive Data Enumeration** protection monitors accounts that rapidly query sensitive data groups (Tax ID, Bank Account Number, Date of Birth). If hundreds of employees query data through one shared ISU, a burst of legitimate traffic or a single runaway query can lock the shared account and take down the tool for everyone.

Learn how to narrow client functional boundaries further in [Scoping Workday API Client Functional Areas for Least-Privilege Access](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping).

## Required Security Domains for Administrators

Before registering or auditing either API client type, verify your administrative security group holds the following domain permissions in the **System** and **Integration** functional areas:

| Administrative Action | Required Security Domain | Functional Area | Permission Type |
| --- | --- | --- | --- |
| Enable OAuth 2.0 in tenant (`Edit Tenant Setup - Security`) | `Set Up: Tenant Setup - Security` | System | Modify |
| Run `Register API Client` or `Register API Client for Integrations` | `Security Administration` | System | Modify |
| Run `View API Clients` and `Manage Refresh Tokens for Integrations` | `Security Administration` | System | View / Modify |
| Create ISUs (`Create Integration System User`) | `Integration Security` | Integration | Modify |
| Edit domain policies & activate changes | `Security Configuration` | System | Modify |

## Decision Checklist: Which Task Should You Run?

Use **Register API Client** (Authorization Code Grant + PKCE) when:

-   Employees, managers, or HR partners query or act on Workday data interactively.
-   You are connecting custom external UIs, BI tools running in user-as-self mode (such as Live Data Query), Workday Studio with MFA, or workforce AI assistants.
-   Every read and write must obey Workday’s native `Employee As Self` and constrained `Manager` security groups.

Use **Register API Client for Integrations** when:

-   A scheduled ETL job, middleware connector, or webhook processor moves records between systems with no human present.
-   Access is intentionally scoped to a dedicated `Integration System Security Group` for a specific interface (such as Workday Data Lake or a Strategic Sourcing connector).

When rolling out workforce tools—such as [Kiweely Bridge](https://kiweely.com/bridge) (coming next for Claude, ChatGPT, and Gemini) or external employee screens in [Kiweely Leaf](https://kiweely.com/leaf) (coming next)—always register a user-delegated client via **Register API Client** with Authorization Code Grant and PKCE so every API call executes strictly under the signed-in employee’s own Workday permissions with zero shared ISU credentials.

## Watch Kiweely Vine connect with an API client for integrations

![Register API Client for Integrations in Workday, as Kiweely Vine connects to a Development tenant](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations/media/vine-api-client-for-integrations-3975d1106e74.webp)

From the film: Register API Client for Integrations in Workday.

In one recorded session against a Workday Development tenant, Kiweely Vine explains each way to connect it to Workday and what to register. A consultant registers an API client and an API client for integrations, generates the client secret and a refresh token, and connects Vine with them.

[Watch the film (11 min)](https://www.youtube.com/watch?v=K_9xp_OImGE) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Can Register API Client for Integrations issue per-employee tokens?

No. Every refresh grant or JWT Bearer assertion on an integration API client authenticates as a designated Integration System User (ISU), never as an interactive employee.

### Which security domains let an administrator register API clients in Workday?

You need Modify access on the Security Administration domain in the System functional area, plus Set Up: Tenant Setup - Security if OAuth 2.0 Clients Enabled is not yet active on Edit Tenant Setup - Security.

### Does Register API Client require a Workday Extend subscription?

No. Both Register API Client and Register API Client for Integrations are core Workday platform tasks available on standard tenants for REST, WQL, SOAP, and RaaS calls.

### Where do I inspect existing API clients in a tenant?

Run the View API Clients report. Standard user-delegated clients appear on the API Clients tab, while ISU-bound clients appear on the API Clients for Integrations tab.

## Sources checked

-   [Workday Admin Guide — Register API Clients](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831010.html)
-   [Workday Admin Guide — Register API Clients for Integrations](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831458.html)
-   [Workday Admin Guide — Edit Tenant Setup - Security](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796470031.html)

## Related guides

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

-   [### Scoping Workday API Client Functional Areas for Least-Privilege Access Workday API Client Scope (Functional Areas) acts as a hard ceiling, never a permission grant: an API request succeeds only when the Functional Area is enabled on the client AND the signed-in worker’s security groups hold permission on the underlying domain or business process.](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [### Calling Workday RaaS Reports with User-Delegated OAuth Instead of an ISU Replace shared Integration System User Basic authentication on Workday Reports as a Service (RaaS) with user-delegated OAuth 2.0 Bearer credentials so custom reports automatically enforce each signed-in worker’s row-level and field-level security.](https://kiweely.com/guides/workday-raas-user-delegated-oauth-vs-isu-basic-auth)
-   [### Managing Workday OAuth Refresh Token Expiration, Rotation, and Revocation Workday rotates user-delegated OAuth refresh tokens on every exchange while enforcing a fixed absolute Refresh Token Timeout measured from initial sign-in. Learn how access TTLs, Enforce 60 Minute Access Token Expiry, and admin revocation tasks work.](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation)
-   [### How to Configure User-Delegated OAuth 2.0 Authorization Code Grant in Workday Register a user-delegated Workday OAuth 2.0 client using Register API Client with Authorization Code Grant, PKCE (S256), and Bearer credentials so external applications authenticate employees through SSO and run under their own Workday permissions.](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup)

### More guides on Integrations and APIs

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

-   [Workday API Attachment Rules: File Size Limits, Allowed MIME Types, and Doctor’s Note Uploads](https://kiweely.com/guides/workday-attachment-upload-virus-scan-size-mime-rules-api)
-   [Submitting and Validating Time-Off Requests with the Workday Absence REST API](https://kiweely.com/guides/workday-absence-management-rest-api-request-time-off)
-   [Reading Current Benefits Elections and Dependents Through Workday Self-Service APIs](https://kiweely.com/guides/workday-view-benefits-elections-dependents-beneficiaries-api)
-   [Auditing External API Calls in Workday Sign-On History and Activity Logs](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)
-   [Entering Time Blocks and Check-In/Check-Out Events via Workday Time Tracking APIs](https://kiweely.com/guides/workday-time-tracking-api-clock-in-out-enter-time)
-   [Authenticating Workday SOAP Web Services with a User-Delegated OAuth Bearer Token](https://kiweely.com/guides/workday-soap-api-bearer-token-user-delegated-oauth)
-   [Diagnosing Workday REST API 403 Forbidden: Missing Client Scope vs. Worker Domain Security](https://kiweely.com/guides/workday-rest-api-403-forbidden-user-security-vs-client-scope)
-   [Workday Expenses REST API: create a Quick Expense, upload a receipt and submit an Expense Report](https://kiweely.com/guides/workday-expenses-rest-api-receipt-attachments-expense-lines)

### From the blog on Integrations and APIs

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

-   [Turning a Messy Client Spreadsheet into a Clean Workday EIB Load in One Conversation](https://kiweely.com/blog/messy-spreadsheet-to-workday-eib-load-with-ai)
-   [Workday REST API vs. SOAP Web Services: Why Setup Work Still Needs the Task Screen](https://kiweely.com/blog/workday-rest-api-vs-soap-coverage-gaps)
-   [Untangling Inherited Workday Studio Integrations: A Practical Modernization Playbook](https://kiweely.com/blog/untangling-inherited-workday-studio-integrations)

## 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.
