> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Raise a work order > Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. ## OpenAPI ````yaml /api-reference/integration.json post /rpc/create_work_order openapi: 3.0.0 info: description: >- The calls an integration needs first. Every endpoint the application uses is in the complete reference. title: Asset Infinity integration API version: 12.2.3 servers: - url: https://app.assetinfinity.ai/api security: [] tags: - description: >- Exchange an API key, or an email and password, for a short-lived session token, and send it as `Authorization: Bearer ` on every other call. name: Signing in - description: >- Where assets are and work happens. A location belongs to a site and may sit inside another location. name: Sites and locations - description: >- The asset register: read it, add to it, correct it, move an asset between sites and locations, and change its status. name: Assets - description: >- Report a problem. A request is triaged by a person, who turns it into a work order or turns it down. name: Work requests - description: >- Raise a job, give it to somebody, move it through the organisation's statuses, complete it and close it. name: Work orders - description: >- Send readings in. A meter reading brings the meter forward and raises any maintenance the usage has made due. A sensor reading can open or clear an alert. name: Meters and sensors - description: >- The part catalogue and what is on the shelf in each store, and the three movements an outside system most often records: a delivery in, an issue out and a correction. name: Parts and stock - description: >- Have the product call your system when something happens, instead of asking it on a timer. name: Webhooks - description: >- The calls behind every register that has no call of its own, answers to the organisation's own fields, and the two calls that answer what to send. `list_options` returns the ids a field accepts. `describe_call` returns the fields any call takes. name: Any record externalDocs: description: PostgREST Documentation url: https://postgrest.org/en/v12/references/api.html paths: /rpc/create_work_order: post: tags: - Work orders summary: Raise a work order description: >- Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. parameters: - $ref: '#/components/parameters/preferParams' requestBody: content: application/json: schema: description: >- Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. properties: p_asset_category_id: format: uuid type: string p_asset_id: format: uuid type: string p_assign_team_id: format: uuid type: string p_assign_vendor_id: format: uuid type: string p_assign_worker_id: format: uuid type: string p_cc_user_ids: format: uuid[] items: type: string type: array p_custom_fields: format: jsonb p_department_id: format: uuid type: string p_description: format: text type: string p_due_at: format: timestamp with time zone type: string p_estimated_duration_minutes: format: integer type: integer p_location_id: format: uuid type: string p_open_now: format: boolean type: boolean p_planned_end_at: format: timestamp with time zone type: string p_planned_start_at: format: timestamp with time zone type: string p_priority_code: format: text type: string p_reported_by_user_id: format: uuid type: string p_requires_permit: format: boolean type: boolean p_safety_instructions: format: text type: string p_severity: format: text type: string p_site_id: format: uuid type: string p_status_id: format: uuid type: string p_title: format: text type: string p_work_order_id: format: uuid type: string p_work_order_type_code: format: text type: string required: - p_title type: object application/vnd.pgrst.object+json: schema: description: >- Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. properties: p_asset_category_id: format: uuid type: string p_asset_id: format: uuid type: string p_assign_team_id: format: uuid type: string p_assign_vendor_id: format: uuid type: string p_assign_worker_id: format: uuid type: string p_cc_user_ids: format: uuid[] items: type: string type: array p_custom_fields: format: jsonb p_department_id: format: uuid type: string p_description: format: text type: string p_due_at: format: timestamp with time zone type: string p_estimated_duration_minutes: format: integer type: integer p_location_id: format: uuid type: string p_open_now: format: boolean type: boolean p_planned_end_at: format: timestamp with time zone type: string p_planned_start_at: format: timestamp with time zone type: string p_priority_code: format: text type: string p_reported_by_user_id: format: uuid type: string p_requires_permit: format: boolean type: boolean p_safety_instructions: format: text type: string p_severity: format: text type: string p_site_id: format: uuid type: string p_status_id: format: uuid type: string p_title: format: text type: string p_work_order_id: format: uuid type: string p_work_order_type_code: format: text type: string required: - p_title type: object application/vnd.pgrst.object+json;nulls=stripped: schema: description: >- Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. properties: p_asset_category_id: format: uuid type: string p_asset_id: format: uuid type: string p_assign_team_id: format: uuid type: string p_assign_vendor_id: format: uuid type: string p_assign_worker_id: format: uuid type: string p_cc_user_ids: format: uuid[] items: type: string type: array p_custom_fields: format: jsonb p_department_id: format: uuid type: string p_description: format: text type: string p_due_at: format: timestamp with time zone type: string p_estimated_duration_minutes: format: integer type: integer p_location_id: format: uuid type: string p_open_now: format: boolean type: boolean p_planned_end_at: format: timestamp with time zone type: string p_planned_start_at: format: timestamp with time zone type: string p_priority_code: format: text type: string p_reported_by_user_id: format: uuid type: string p_requires_permit: format: boolean type: boolean p_safety_instructions: format: text type: string p_severity: format: text type: string p_site_id: format: uuid type: string p_status_id: format: uuid type: string p_title: format: text type: string p_work_order_id: format: uuid type: string p_work_order_type_code: format: text type: string required: - p_title type: object text/csv: schema: description: >- Raise a job with no request behind it — a breakdown somebody is standing in front of. It opens, as every work order does. On the offline allowlist, so a handset in a basement can raise one and the server applies it when the signal comes back. It asks what the edit form asks: one list of questions, so nothing appears for the first time after the job exists — the eight columns and the tenant's own fields both, the second answered through the same customFields a record edit takes. The status is the exception and is not an argument — a job opens where the state model starts records. properties: p_asset_category_id: format: uuid type: string p_asset_id: format: uuid type: string p_assign_team_id: format: uuid type: string p_assign_vendor_id: format: uuid type: string p_assign_worker_id: format: uuid type: string p_cc_user_ids: format: uuid[] items: type: string type: array p_custom_fields: format: jsonb p_department_id: format: uuid type: string p_description: format: text type: string p_due_at: format: timestamp with time zone type: string p_estimated_duration_minutes: format: integer type: integer p_location_id: format: uuid type: string p_open_now: format: boolean type: boolean p_planned_end_at: format: timestamp with time zone type: string p_planned_start_at: format: timestamp with time zone type: string p_priority_code: format: text type: string p_reported_by_user_id: format: uuid type: string p_requires_permit: format: boolean type: boolean p_safety_instructions: format: text type: string p_severity: format: text type: string p_site_id: format: uuid type: string p_status_id: format: uuid type: string p_title: format: text type: string p_work_order_id: format: uuid type: string p_work_order_type_code: format: text type: string required: - p_title type: object required: true responses: '200': description: OK components: parameters: preferParams: description: Preference in: header name: Prefer required: false schema: enum: - params=single-object type: string ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.