Work Orders
Work orders represent service work and field operations in your CRM. They track work to be performed, often linked to projects or customer requests.
Use the Activity_WorkOrder endpoint to manage work orders. Work orders inherit all fields from Activity.
Endpoints
List Work Orders
GET
/v1/odata/Activity_WorkOrderSingle Work Order
GET
/v1/odata/Activity_WorkOrder({id})Create Work Order
POST
/v1/odata/Activity_WorkOrderUpdate Work Order
PUT
/v1/odata/Activity_WorkOrder({id})Delete Work Order
DELETE
/v1/odata/Activity_WorkOrder({id})Fields
Inherited Fields (from Activity)
See Activity Fields for all inherited fields.
Relationships
| Relationship | Target Entity | Cardinality | Description |
|---|---|---|---|
| Relationship | Relationship | N:1 | Linked relation |
| Contact | Relation.Person.Contact | N:1 | Contact person |
| Phase | Datastore.Phase.ActivityWorkOrder | N:1 | Work order phase |
| LinkedActivities | Activity | 1:N | Linked activities |
| TimeRegistrations | TimeRegistration | 1:N | Time registrations |
Expanding Relationships
GET
/v1/odata/Activity_WorkOrder({id})?$expand=RelationshipNavigating Relationships
GET
/v1/odata/Activity_WorkOrder({id})/RelationshipFiltering Examples
GET
/v1/odata/Activity_WorkOrder?$filter=contains(Subject, '{Subject}')&$top={top}GET
/v1/odata/Activity_WorkOrder?$filter=IsClosed eq {IsClosed}&$top={top}GET
/v1/odata/Activity_WorkOrder?$filter=CreationDate gt {CreationDate}&$top={top}Custom Query
Build your own OData query against Activity_WorkOrder. Open Run and edit the whole request inline — swap the entity set, change the $filter, or add $expand, $select, $orderby, $top, $skip. Type $ for suggestions; use ↺ Reset to restore this example.
GET
/v1/odata/Activity_WorkOrder?$top=10