Workday Studio HTTP-Out DELETE Call Returns 415 Unsupported Media Type
What it means
A Workday Studio integration that calls an external REST API using an http-out component's DELETE method receives a 415 Unsupported Media Type response, even though the exact same JSON payload, headers, and bearer token work correctly from Postman or Bruno, and even though POST and GET calls from the same Studio integration to the same API succeed. The failure is specific to how Studio's http-out component builds the DELETE request itself, not the target API or the credentials.
Troubleshooting
- Confirm POST and GET calls from the same http-out component and credentials succeed against the same API, to isolate the problem to the DELETE method specifically rather than authentication or connectivity.
- Compare the exact request headers Studio sends on the DELETE call against what Postman or Bruno send, particularly Content-Type, since some HTTP client implementations omit or alter the Content-Type header on DELETE requests that include a body.
- Check whether the http-out component's DELETE configuration is actually attaching the JSON body to the outgoing request at all, since some REST client implementations silently drop the body on DELETE unless explicitly configured to send one.
- If Studio's http-out DELETE handling cannot be made to send the body and headers exactly as Postman does, check whether the external API also accepts the same operation via POST with a method-override header, as a workaround specific to that endpoint.
Explicitly set the Content-Type header to application/json on the http-out DELETE step's configuration rather than relying on Studio's default behavior for that method.
When integrating with an external REST API that expects a body on DELETE, verify Studio's http-out component sends an identical request, matching headers, body, and method, to what a REST client trace shows before relying on it in production, since DELETE-with-body handling is inconsistent across HTTP client implementations.