Body This is the limit of the work orders.
This is the offset of the work orders.
This is the order direction of the work orders.
Response Unique identifier for the work order (primary key)
Number associated with the work order
Site or location where the work order is being executed
Location or site where the work order is applicable
Part or item associated with the work order
Identifier or reference to the order associated with the work order
Identifier or reference to the manufacturing order associated with the work order
Current status or state of the work order
Name or identifier of the person who created the work order
Date and time when the work order was created
Date and time when the work order was last updated
Date when the work order was issued
Expected completion date for the work order
Priority level or urgency of the work order
Memo or additional notes related to the work order
Number associated with the bill of materials related to the work order
Actual labor hours spent on the work order
Standard labor hours for the work order
Identifier for related capacity utilization data
Identifier for related bill of materials
Identifier for related COGS (Cost of Goods Sold) data
Response Indicates whether the call was successful. 1 if successful, 0 if not.
The contents of the user group This is the internal ID for this user group. You don’t need to record this
information, since you will not need to use it.
This is the user group token (userGroupToken or USER_GROUP_TOKEN) that will be
used to identify which user group is viewing the dashboard. You should save
this on your end to use when rendering an embedded dashboard.
This is the name of the user group provided in the request body.
This is the user_group_id provided in the request body.
This is the environment tag of the user group. Possible values are ‘Customer’
and ‘Testing’. User group id’s must be unique to each environment, so you can
not create multiple user groups with with same id. If you have a production
customer and a test user group with the same id, you will be required to label
one as ‘Customer’ and another as ‘Testing’
cURL
GraphQL
Node.js
Python
Ruby
PHP
Go
Java
curl --location --request POST 'https://api.stateset.com/v1/work_order' \ --header 'Content-Type: application/json' \ --header 'Authorization: Token <token>' \ --data-raw '{ "bill_of_materials_number": "123", "created_at": "2021-01-01T00:00:00.000Z", "created_by": "John Doe", "expected_completion_date": "2021-01-01T00:00:00.000Z", "id": "wo_123", "issue_date": "2021-01-01T00:00:00.000Z", "location": "123", "manufacture_order": "123", "memo": "123", "number": "123", "order_number": "123", "part": "123", "priority": "123", "site": "123", "status": "123", "updated_at": "2021-01-01T00:00:00.000Z", "work_order_line_items": [ { "id": "wo_123", "line_status": "123", "line_type": "123", "part_name": "123", "part_number": "123", "total_quantity": "123", "unit_quantity": "123", "work_order_number": "123" } ] }'
{ { "bill_of_materials_number" : "123" , "created_at" : "2021-01-01T00:00:00.000Z" , "created_by" : "John Doe" , "expected_completion_date" : "2021-01-01T00:00:00.000Z" , "id" : "wo_123" , "issue_date" : "2021-01-01T00:00:00.000Z" , "location" : "123" , "manufacture_order" : "123" , "memo" : "123" , "number" : "123" , "order_number" : "123" , "part" : "123" , "priority" : "123" , "site" : "123" , "status" : "123" , "updated_at" : "2021-01-01T00:00:00.000Z" , "work_order_line_items" : [ { "id" : "wo_123" , "line_status" : "123" , "line_type" : "123" , "part_name" : "123" , "part_number" : "123" , "total_quantity" : "123" , "unit_quantity" : "123" , "work_order_number" : "123" } ] } } 