Manage projects for work order templates and configuration.
Projects represent specific initiatives (e.g., "Q4 POS Rollout", "Network Refresh 2024"). They can enforce default templates, pay rates, and selection rules for all work orders assigned to them.
GET /projects
{
"results": [
{
"id": 501,
"name": "Q4 POS Rollout",
"client_id": 102,
"active": true,
"work_orders_count": 45,
"template_id": 88
}
]
}POST /projects
{
"name": "Network Refresh 2024",
"client_id": 102,
"template_id": 88,
"description": "Nationwide router replacement initiative"
}Projects can enforce:
| Setting | Description |
|---|---|
template_id | Default work order template |
pay_rate | Standard pay for the project |
talent_pool_group_id | Preferred provider group |
selection_rules | Auto-assignment criteria |
Assign a work order to a project to inherit its settings:
{
"title": "Site #44 - Router Install",
"project": { "id": 501 },
"client": { "id": 102 }
}Best Practice: Create projects in the Field Nation UI where you can configure complex settings, then reference the project_id in your API integration.
You can add multiple providers to a project's talent pool:
POST /projects/{project_id}/providers
{
"provider_ids": [123, 456, 789]
}Last updated on