Studio workday-out-rest: Custom Object Endpoint Path Not Resolving
The error HTTP 404 Not Found. The requested resource could not be found.
What does "HTTP 404 Not Found. The requested resource" mean in Workday Studio?
The workday-out-rest component needs a specific path segment beyond the base URL for custom object endpoints. Leaving the path blank or using just the base REST URL gives you a 404. The correct path includes the custom object alias and - for GET - a specific object ID.
Quick fix
Use the Select a Custom Object button in the component to auto-populate the correct endpoint path, test with GET on one record, then switch to the right HTTP method.
Permanent fix
Document the custom object alias and full endpoint path in the integration design doc. Store a working GET call as a reference assembly in your Studio workspace so future rebuilds don't require rediscovery.
Troubleshooting
- Open the workday-out-rest component and check the Path field - it needs the custom object alias path segment, not just the base Workday URL.
- Use the Select a Custom Object button (set method to GET), connect to your environment, pick the object alias and a test ID - Studio auto-populates the correct path.
- Deploy and run with a known worker WID to confirm the path resolves before wiring it into the full assembly.
- For PUT or POST, copy the path pattern from the GET configuration - the alias segment is the same.
Was this helpful?