Understand the Work Order lifecycle, key concepts, and resource prerequisites.
A Work Order is the fundamental unit of work in the Field Nation ecosystem. It represents a job to be done, a contract between a Buyer and a Provider, and a record of the work performed.
This section covers the Client API endpoints for creating and managing work orders.
Before diving into the endpoints, it's crucial to understand a few key terms:
| Term | Definition |
|---|---|
| Buyer | You (or your client). The entity creating the work order and paying for the work. |
| Provider | The technician or contractor who performs the work. |
| Marketplace | The open network of providers. You can "Route" work to the marketplace to find new talent. |
| Private Network | Your curated list of preferred providers. |
| Draft | The initial state of a work order. Visible only to you. |
| Routed | The state where work is available for providers to request. |
| Assigned | The state where a specific provider is contracted to do the work. |
A work order acts as a state machine. You move it through specific stages using API actions.
To successfully create and manage work orders, you will need to reference other resources. You cannot usually just "guess" IDs.
Ensure you have a valid Oauth2 access token.
Most dropdowns or ID fields in the Work Order payload come from these lookup endpoints:
GET /types-of-work (Required for creation)GET /service-contracts (Who pays for this?)GET /projects (Optional organization)If you plan to route to specific people, you need their IDs:
GET /providers or GET /talent-poolsStart by learning how to construct the work order payload.
Last updated on