Hi community, just curious is there a way or a document somewhere to view the minimum field required for all post/patch api requests , I only have seen this one documented in the D

Originally replied by Brenda Sutton on Jun 4, 2026, 8:18 AM.

Hi @Mark Tan​, The short answer is: not universally. The POST Employee endpoint is one of the few endpoints where the minimum required fields are clearly documented and a sample is provided. For most other POST and PATCH endpoints, the required fields are typically defined within the endpoint's request schema in the API Explorer/DDN documentation rather than in a consolidated "minimum required fields" reference document.

A common approach is to:

• Review the request model/schema for the specific endpoint in API Explorer.
• Check the endpoint-specific examples provided in DDN.
• Test against a non-production environment, as some fields may be conditionally required based on tenant configuration, feature enablement, or referenced XRefCodes.

I'm not aware of a single Dayforce document today that lists the minimum required fields for all POST/PATCH endpoints in one place. If anyone in the community has found such a reference, I'd be interested as well. This question comes up often; I'll look to see if there is a way we can build a document together with feedback from others within the community. It would be great to start with the top 5-10 endpoints and build from there. Stay tuned:-)

Originally replied by Eddie Heinzelman on Jun 4, 2026, 12:11 PM.

Mark, I know it's not the same, but I also reference the Import specs as a general guideline because there may be more than the minimum required fields that need to be addressed. For example, we did an API for POST/PATCH of Projects. The DDN doesn't outline required fields and there are fields that you have to send even if it's blank (we sent the value as [ ] ) - so we used the ProjectImport specifications to understand which fields were marked as required on the screen then worked from there as we tested. This may not be a universal way to look at them, but just a suggestion to check some of the field that may need special attention.

Originally replied by Shane Zahra on Jul 16, 2026, 11:38 PM.

Hi @Brenda Sutton​ If there is a central shared document with partners, I would be interested being involved.

Originally replied by Mark Tan on Jun 5, 2026, 2:59 AM.

Thank you @Brenda Sutton​  and @Eddie Heinzelman​ for sharing that information! the details you provided are a solid starting point, super helpful! still hoping we can see some reference in the near future on this topic.