---
title: "Workday Sandbox Refresh Impact on API Clients — Kiweely"
description: "What happens to API Client registrations, Client IDs, Authorize and Token URLs, and callback URIs when Workday refreshes your Sandbox tenant from Production."
url: https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts
---

# How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs

A weekly Workday Sandbox refresh overwrites Sandbox with an exact copy of Production, wiping any API Client registered only in Sandbox while copying Production API Clients—along with their Client IDs, secrets, and Production callback URIs—into Sandbox.

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

When Workday refreshes your Sandbox tenant during the weekly maintenance window, it does not merge configuration—it replaces the entire Sandbox instance with a point-in-time snapshot of Production. Any OAuth client created only in Sandbox disappears on Monday morning, while every **API Client** registered in Production copies down into Sandbox with its Production **Client ID**, **Scope (Functional Areas)**, and **Redirection URI** intact.

Teams building external portals, analytics pipelines, or AI integrations run into two opposite failures right after a refresh: either their test client vanishes (`invalid_client`), or a copied Production client redirects Sandbox sign-ins straight back into a live Production callback endpoint. Understanding exactly which OAuth properties are tenanted data versus host-derived URLs eliminates post-refresh outages completely.

## Artifact-by-Artifact Impact of a Sandbox Refresh

Use this reference matrix to audit what survives, what gets wiped, and what changes value when Production overwrites Sandbox (or when an Implementation or Sandbox Preview tenant refreshes):

| OAuth / Security Artifact | Created Only in Sandbox | Created in Production Before Refresh | Post-Refresh Action Required |
| --- | --- | --- | --- |
|  **Register API Client** entry (Authorization Code / PKCE) |  **Deleted** |  **Copied to Sandbox** with identical Client ID and Client Secret | Register persistent clients in Production (or disable/restrict per environment), or recreate temporary Sandbox clients |
|  **Register API Client for Integrations** entry |  **Deleted** |  **Copied to Sandbox** with identical Client ID | Regenerate or verify ISU refresh grants in Sandbox if you rotate integration secrets |
|  **Authorization Endpoint** & **Token Endpoint** |  **Deleted** with the client |  **Rewritten automatically** in **View API Clients** to reflect the Sandbox host and tenant alias | Point your staging app at the Sandbox `/authorize` and `/oauth2/{sandbox_tenant}/token` URLs |
|  **Redirection URI** list on the API Client |  **Deleted** |  **Copied verbatim** from Production | Include staging/localhost URIs carefully or maintain dedicated non-production callback routes |
|  **Disabled on Tenants** / client enablement flags |  **Deleted** |  **Copied verbatim** from Production | Verify environment restrictions on integration clients so Sandbox jobs cannot run unintended external syncs |
|  **OAuth 2.0 Refresh Tokens** issued in Sandbox |  **Invalidated / Wiped** | Production user sessions do not grant live Sandbox access tokens without re-authorizing against Sandbox | Interactive users sign in once on the Sandbox authorize URL; rotate ISU tokens in **Manage Refresh Tokens for Integrations** |
|  **Edit Tenant Setup - Security** SAML IdPs & Redirect URLs |  **Overwritten** by Production |  **Copied**, honoring **Used for Environments** and **Preview Only** flags | Configure **Sandbox** environment rows in Production so SSO works immediately after every refresh |
|  **Developer Site Console** API Clients (Extend / WCP) | Unaffected (stored in Developer Site account, not tenant DB) | Governed by **Modify Authorized Tenants** allowlist | Ensure the Sandbox tenant alias remains on the Company Administrator’s authorized tenant allowlist |

For the broader mechanics of weekly Sandbox vs. semi-annual Sandbox Preview vs. on-demand Implementation refreshes, see [what a Workday Sandbox refresh wipes](https://kiweely.com/guides/workday-sandbox-refresh) and [Workday tenant types explained](https://kiweely.com/guides/workday-tenant-types).

## Why Sandbox-Only API Clients Vanish Every Weekend

In Workday’s architecture, anything created via **Register API Client** or **Register API Client for Integrations** is **tenanted data**, just like a custom report, calculated field, or security group. Because the standard Sandbox refreshes every weekend from Production:

1.  On Thursday, an administrator runs **Register API Client** in Sandbox, copies the generated `Client ID`, and wires a staging web app to Sandbox.
2.  Over the weekend, Workday replaces Sandbox with Production’s database.
3.  On Monday morning, that `Client ID` no longer exists anywhere in Sandbox’s **View API Clients** report. Every OAuth `/authorize` call fails immediately, and token exchanges return `invalid_client`.

If you are iterating on a multi-week build and are not ready to create the client registration in Production, build against an **Implementation** tenant instead. Implementation tenants only refresh on demand through Customer Central or a support request, giving you a stable Client ID until cutover. Note that **Object Transporter** (OX 2.0) does not migrate OAuth client secrets or active refresh grants across tenants—treat API Client registration as an explicit environment cutover checklist item, as detailed in [copying configuration between Workday tenants](https://kiweely.com/guides/workday-configuration-between-tenants).

## How Production Redirect URLs Cause Cross-Environment Collisions

Once an integration or employee application goes live in Production, its **API Client** exists in Production—which means every weekly refresh copies that registration into Sandbox. That solves the vanishing Client ID problem, but introduces a subtle redirect trap:

-   Workday dynamically updates the **Workday REST API Endpoint**, **Token Endpoint**, and **Authorization Endpoint** displayed on **View API Clients** to match the current tenant’s hostname and tenant name.
-   Workday does **not** rewrite the **Redirection URI** or **Allowed Origins** (CORS) fields you typed into the **API Client** definition.

Suppose your Production API Client only lists `https://portal.company-domain.example/oauth/callback` as its **Redirection URI**. When a developer initiates an OAuth sign-in against the Sandbox **Authorization Endpoint** using that copied `Client ID`:

http

```
GET /{sandbox_tenant}/authorize?response_type=code&client_id=copied_prod_client_id&redirect_uri=https://staging-portal.company-domain.example/oauth/callback&code_challenge=...&code_challenge_method=S256 HTTP/1.1
```

Workday rejects the request because `https://staging-portal.company-domain.example/oauth/callback` is not registered on the client. Worse, if the developer omits `redirect_uri` (which Workday treats as optional when a single URI is registered), Workday authenticates the user in **Sandbox** and then sends the `302 Found` redirect—carrying a Sandbox authorization `code`—to the **Production** callback server, where the token exchange fails because the Production server tries to redeem a Sandbox code against the Production token endpoint.

### Two Clean Patterns for Production-to-Sandbox Survival

Pick one of these two patterns depending on your security team’s posture:

1.  **Environment-specific API Clients registered in Production with tenant scoping:** Register two distinct clients in Production—for example, `Portal User OAuth (Prod)` with your Production callback URI, and `Portal User OAuth (Non-Prod)` with your staging callback URI. Disable or restrict the non-production client in Production, and after a Sandbox refresh, enable only the non-production client in Sandbox via **Edit API Client** from **View API Clients**.
2.  **Tenant-aware router callback (used by multi-tenant cloud platforms):** Register a single HTTPS callback endpoint controlled by an environment-aware proxy that validates the cryptographic `state` parameter tied to the originating tenant session, ensuring a Sandbox `code` is only ever redeemed against that exact Sandbox tenant’s token endpoint.

## SSO Redirection URLs and SAML IdP Survival in Edit Tenant Setup - Security

Even when your OAuth **API Client** and **Redirection URI** are right, user-delegated OAuth still fails after a Sandbox refresh if corporate SSO redirects Sandbox users to a Production-only SAML Identity Provider assertion consumer URL.

Unlike **Register API Client**, Workday built explicit environment awareness directly into **Edit Tenant Setup - Security** so you can configure SSO once in Production and never touch it after a refresh:

1.  Open **Edit Tenant Setup - Security** in Production (requires **Set Up: Tenant Setup - Security** in the **System** functional area).
2.  Under **Single Sign-On** → **Redirection URLs**, add separate rows by selecting **Sandbox** or **Implementation** at the **Environment** prompt (which also governs **Sandbox Preview** and **Implementation Preview** respectively). If a Preview tenant needs a distinct URL from standard Sandbox, add a second row for that environment and check **Preview Only**.
3.  Under **SAML Setup** → **SAML Identity Providers**, populate **Used for Environments** (`Production`, `Sandbox`, `Implementation`) on each IdP row so Workday automatically activates the Sandbox SAML trust relationship the moment Production copies into Sandbox.

## Refresh Survival for External Employee Apps and AI Connectors

Whenever an external platform connects to both Production and non-production Workday tenants, verify how it isolates tenant routes across refreshes. Both [Kiweely Bridge](https://kiweely.com/bridge) (coming next, where one company plan covers Production plus every Sandbox, Sandbox Preview, and Implementation tenant) and [Kiweely Leaf](https://kiweely.com/leaf) (coming next) bind each tenant connection to its own explicit Workday authorize and token endpoints under user-delegated OAuth, so a weekly Sandbox refresh never crosses credentials or mixes staging tests with live Production worker records.

## Post-Refresh Verification Checklist

Run these five checks in Sandbox after any scheduled or ad-hoc refresh before handing the environment back to testers:

1.  Open **View API Clients** in Sandbox and confirm your expected **Client ID** is present, enabled, and lists the staging **Redirection URI** and **Allowed Origins**.
2.  Copy the **Authorization Endpoint** and **Token Endpoint** directly from Sandbox’s **View API Clients** screen rather than editing Production hostnames by hand (Sandbox often sits on a different Workday data center host than Production).
3.  Verify on **Edit Tenant Setup - Notifications** that email, push, and SMS restrictions are active so API-triggered business processes in Sandbox cannot notify real workers.
4.  Confirm SAML sign-in completes on the Sandbox **Authorization Endpoint** without bouncing to the Production tenant login screen.
5.  Complete one end-to-end PKCE authorization code exchange as a test worker and confirm the resulting Bearer grant reads data solely from the Sandbox tenant.

## Frequently asked questions

### Why did my Sandbox OAuth Client ID stop working on Monday morning?

Workday refreshes the standard Sandbox tenant every weekend by replacing it completely with a fresh snapshot of Production. Any API Client created only in Sandbox and never registered in Production is erased during the refresh, causing Monday OAuth requests to fail with invalid\_client.

### Does a Production API Client keep the same Client ID in Sandbox after a refresh?

Yes. Tenanted API Clients created via Register API Client or Register API Client for Integrations in Production are copied into Sandbox with the exact same Client ID and Functional Area scopes, while Workday automatically rewrites the Token Endpoint and Authorization Endpoint on View API Clients to use the Sandbox host and tenant name.

### If Production API Clients copy to Sandbox, can a Sandbox test accidentally hit Production?

Only if your external application keeps calling the Production Token or REST base URL, or if the copied API Client only lists a Production Redirection URI so the OAuth browser callback lands on your live Production server instead of your staging environment.

### How do Developer Site API Clients behave differently from tenant-registered API Clients during a refresh?

API Clients created in the Workday Extend Developer Site Console live outside individual tenant data and govern access through a Company Administrator tenant allowlist (Modify Authorized Tenants), whereas tenant-registered clients created in Register API Client are tenanted objects that get overwritten whenever Sandbox refreshes from Production.

## Sources checked

-   [Workday Tenants and Tools](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)
-   [Reference: Edit Tenant Setup - Security](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796470031.html)
-   [Steps: Update Workday Data Source and Credential After Tenant Refreshes](https://doc.workday.com/admin-guide/en-us/adaptive-planning/set-up-adaptive-planning-for-hcm-and-financials/adaptive-planning-tenant-refreshes/fec1595444879620.html)
-   [Create Your API Client](https://developer.workday.com/documentation/zwx1518028675482)

## Related guides

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

-   [### How to Authenticate Workday Studio and External Tools Using an OAuth API Client with PKCE (When SSO Blocks Passwords) When SSO leaves consultants without a Workday password, register an API Client with Authorization Code Grant and Support Proof Key for Code Exchange enabled, then use that client ID with Studio or Vine OAuth sign-in instead of username and password auth.](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password)
-   [### What are the types of tenant in Workday? Sandbox, Sandbox Preview, Implementation and Production compared Most Workday customers get four tenants: Production, Sandbox, Sandbox Preview and Customer Central. Implementation and demonstration tenants cost extra. Sandbox refreshes weekly from Production, Preview twice a year, Implementation on demand.](https://kiweely.com/guides/workday-tenant-types)
-   [### When does the Workday Sandbox refresh, and what does it wipe? Weekly: Workday replaces the Sandbox with a full copy of Production data and configuration. Public Workday docs give no day or hour, so ask your tenant management contact. Preview refreshes twice a year, Implementation on demand.](https://kiweely.com/guides/workday-sandbox-refresh)
-   [### What is the safest way to copy Workday configuration from one tenant to another? Use Object Transporter, launched from the object or from Customer Central, and read its error check, prerequisite check and diff report before migrating. Use Configuration Change Tracker for project work and extracts only for different billing IDs.](https://kiweely.com/guides/workday-configuration-between-tenants)

### More guides on Integrations and APIs

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

-   [Register API Client vs. Register API Client for Integrations in Workday](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-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)
-   [Scoping Workday API Client Functional Areas for Least-Privilege Access](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [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)

### From the blog on Integrations and APIs

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

-   [What Is an AI-Built Workday Integration Platform Outside the Tenant?](https://kiweely.com/blog/what-is-ai-built-workday-integration-platform)
-   [Nothing Kept After a Run: Zero-Retention Workday Integrations](https://kiweely.com/blog/nothing-kept-after-a-run-zero-retention-integrations)
-   [Retire Workday Studio and EIB Debt with External Integrations](https://kiweely.com/blog/retire-workday-studio-eib-debt-with-external-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.
