Field NationDeveloper Platform
Field NationDeveloper Platform
IntroductionQuick StartAPI Playground

Getting Started

API Reference

Overview
LifecycleAssignmentsProvider ActionsSmart Dispatch
Work OrdersWorkflow

Lifecycle

Publish, Route, Assign, and complete work orders.


Workflow Lifecycle

Once a work order is created, you must move it through its lifecycle using specific API actions.

State Diagram

Loading diagram...

1. Publish

A work order starts in Draft state. It is invisible to anyone but you. Publishing changes the state to Open (or Routed), making it visible to the providers you route it to.

POST /workorders/{id}/publish

You can also unpublish a work order to return it to Draft state using DELETE /workorders/{id}/publish.

2. Route vs. Assign

You have two primary ways to fill a work order:

  1. Route (Marketplace/Network): Invite multiple providers to request the work. You review requests and select the best fit.
  2. Assign (Direct): You already know who you want. You bypass the request phase and directly contract a specific provider.

Use Route when you need to find talent or get competitive offers. Use Assign when you have a dedicated W-2 employee or a preferred contractor you've already spoken with.

Routing

Routing sends the work order to specific providers or groups, inviting them to request the work.

POST /workorders/{id}/route

Routing to a Provider

{
  "technician": { "id": 12345 }
}

Mass Routing

To route to many providers at once (e.g., a Talent Pool), use the mass-route endpoint.

POST /workorders/{id}/mass-route

{
  "talent_pool_id": 9921
}

Auto Dispatch

Automatically routes the work order based on pre-defined rules.

POST /workorders/auto_dispatch

Selection Rules

When routing, you can apply Selection Rules to filter providers.

{
  "selection_rule": {
    "rules": [
      { "name": "rating", "operator": ">=", "value": 4.5 }
    ]
  }
}

3. Assign

See Assignments for detailed assignment management.

POST /workorders/{id}/assignee

4. Closing the Loop

Approve

If satisfied with the work, approve to release payment.

POST /workorders/{id}/approve

Incomplete

If unsatisfied, mark it incomplete to send it back.

DELETE /workorders/{id}/complete

Required Params:

  • reason: Text description
  • reason_id: The ID of the incomplete reason

Use GET /company/{id}/reasons/incomplete to get valid Reason IDs for your company.

API Quick Reference

ActionEndpointMethod
Publish/workorders/{id}/publishPOST
Unpublish/workorders/{id}/publishDELETE
Route to provider/workorders/{id}/routePOST
Mass route/workorders/{id}/mass-routePOST
Auto dispatch/workorders/auto_dispatchPOST
Assign/workorders/{id}/assigneePOST
Approve/workorders/{id}/approvePOST
Mark incomplete/workorders/{id}/completeDELETE

Related

  • Assignments - Detailed assignment management
  • Create Work Order - Creating work orders
  • Revisits - Handling incomplete work
  • Company Settings - Incomplete reasons

Last updated on

Update & Cancel

Updating, canceling, and managing work orders.

Assignments

Managing provider assignments, requests, and counter-offers.

On this page

Workflow Lifecycle
State Diagram
1. Publish
2. Route vs. Assign
Routing
Routing to a Provider
Mass Routing
Auto Dispatch
Selection Rules
3. Assign
4. Closing the Loop
Approve
Incomplete
API Quick Reference
Related