---
title: "Why does a custom object update return 403 with escaped…"
description: "A custom object update can return 403 when the client re-encodes escaped HTML in the JSON body. Send raw application/json and use PUT as documented."
url: https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html
---

# Why does a custom object update return 403 with escaped HTML in the body?

Custom Object updates use PUT. A 403 with escaped HTML in the body is usually client double-encoding, not missing domains. Send raw application/json and validate the document before retrying.

-   **Checked** against Workday on November 17
-   Applies to **Workday Custom Object REST APIs**
-   2 min read
-   Published November 17
-   By Kiweely

A custom object update that returns **403 Forbidden** when the body carries a large block of escaped HTML—while the same field accepts short plain text—is usually a **request-body encoding** problem, not a missing security group. Fix how the JSON is serialized before you rewrite domain policies.

## What Workday documents for updates

Workday’s Custom Object REST APIs update a single-instance or multi-instance object with:

http

```
PUT /customObjects/{customObjectAlias}/{customObjectID}
```

The docs state these APIs do not cover effective-dated custom objects (use the SOAP additional-data path for those). Request bodies must use the correct field types: quoted strings for text, unquoted numbers and booleans, `yyyy-mm-dd` for dates. PUT updates only the fields you send.

If your tooling labels the verb as PATCH, confirm you are calling an API that actually documents PATCH. For the Custom Object service Workday publishes, the update method is **PUT**.

## Separate security failures from body failures

| Test | If it succeeds | If it fails |
| --- | --- | --- |
| Same user, short plain text in the field | Security path can update the object | Fix domain / ISSG access first |
| Long plain text without markup | Length alone is not the blocker | Look at size limits or timeouts next |
| Same long value with HTML / escaped quotes | Encoding is the suspect | Send raw JSON; stop double-escaping |

Workday also documents `x-validate-only: 1` on POST, PUT, and DELETE to validate without persisting. Use that to test body shape without writing data.

## Fix the body serialization

1.  Build the JSON with a proper encoder so HTML inside a string is escaped exactly once.
2.  In interactive API clients, switch the body type to **raw** and set `Content-Type: application/json` yourself instead of a “JSON” mode that re-encodes an already escaped string.
3.  Validate the document in a separate parser before sending. One broken quote inside the HTML breaks the whole body.
4.  Retry with PUT to the documented `/customObjects/...` URL and the web service alias from **View Custom Object**.
5.  If it still fails after a clean body, then inspect security on the custom object’s domain and the caller (user or ISU).

When an Extend page performs the update, map errors with `responseErrorDetail` and include 403 in `failOnStatusCodes` so the page shows Workday’s detail instead of a bare failure.

Kiweely Vine can help you draft and validate Extend or integration calls against a connected tenant with consent. It does not bypass Custom Object security.

## Frequently asked questions

### Does Workday document PATCH for custom objects?

The Custom Object REST API docs describe GET, POST, PUT, and DELETE. Updates use PUT /customObjects/{alias}/{id}. Prefer PUT unless another documented API you call explicitly uses PATCH.

### Why does plain text work but HTML in the same field fail?

Security is likely fine. The client’s JSON editor often re-encodes quotes inside escaped HTML and corrupts the body. Send raw application/json built by a real JSON library.

### How do I update only some fields?

PUT updates only the fields you include. Omitted fields are left as they are. To clear a field to null, Workday says to delete and recreate the instance without that field.

## Sources checked

-   [Custom Object (Single-Instance) REST APIs](https://developer.workday.com/documentation/vjs1621308998420)
-   [Custom Object (Multi-Instance) REST APIs](https://developer.workday.com/documentation/izr1621310982493/CustomObjectMultiInstanceRESTAPIs)
-   [Concept: Custom Objects](https://developer.workday.com/documentation/fdy1529428780920)
-   [responseErrorDetail](https://developer.workday.com/documentation/lgo1595000847400/responseErrorDetail)

## Related guides

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

-   [### Why does an Extend edit page show Internal Server Error on submit? A bare Internal Server Error on submit hides an outbound endpoint failure. Read Analytics Logs, fix the payload or security, and map responseErrorDetail—including failOnStatusCodes for 400/403.](https://kiweely.com/guides/workday-extend-internal-server-error-on-submit)
-   [### Parsing Workday Business Process Custom Validation Errors Returned by REST and SOAP APIs Workday REST APIs return HTTP 400 JSON payloads containing an errors array with code, field, path, and severity (Critical or Warning), whereas Workday SOAP Web Services return HTTP 500 envelopes containing Validation\_Fault (with Xpath) or Processing\_Fault elements.](https://kiweely.com/guides/workday-business-process-validation-errors-rest-soap-responses)

### More guides on Integrations and APIs

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

-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [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)

### From the blog on Integrations and APIs

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

-   [Before-and-After Diffs and One-Step Rollback for Integration Fixes](https://kiweely.com/blog/before-and-after-diffs-and-one-step-rollback)
-   [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)

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