How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Automile ResourceOwnerWorkOrder API

The ResourceOwnerWorkOrder API from Automile — 12 operation(s) for resourceownerworkorder.

Automile ResourceOwnerWorkOrder API is one of 78 APIs that Automile publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ResourceOwnerWorkOrder. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 24 operations across 12 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.automile.com/.

24 operations 12 paths 27 schemas 4 DELETE10 GET5 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.automile.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Automile ResourceOwnerWorkOrder API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the implicit flow, exposing 2 scopes.

  • oauth2 — OAuth2 Implicit Grant

Paths & Operations 24

Across 12 paths, the API surfaces 24 operations — 4 DELETE, 10 GET, 5 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

ResourceOwnerWorkOrder 24
GET
/v1/resourceowner/workorders
Retrieve a list of work orders and their containing attachments, items and notes
ResourceOwnerWorkOrder_GetWorkOrderList 5 params → 200500
POST
/v1/resourceowner/workorders
Create a work order and containing attachments, items and notes
ResourceOwnerWorkOrder_CreateWorkOrder body → 200201500
PUT
/v1/resourceowner/workorders
Update or create one or many work orders
ResourceOwnerWorkOrder_SaveWorkOrderList body → 200500
GET
/v1/resourceowner/workorders/{workOrderId}
Retrieve a work order
ResourceOwnerWorkOrder_GetWorkOrder 1 param → 200500
PUT
/v1/resourceowner/workorders/{workOrderId}
Update a work order
ResourceOwnerWorkOrder_UpdateWorkOrder 1 param body → 200403500
DELETE
/v1/resourceowner/workorders/{workOrderId}
Delete work order
ResourceOwnerWorkOrder_DeleteWorkOrder 1 param → 200403500
GET
/v1/resourceowner/workorders/getwithquoteid/{quoteId}
Retrieve a work order by quote id
ResourceOwnerWorkOrder_GetWorkOrderByQuoteId 1 param → 200500
POST
/v1/resourceowner/workorders/{workOrderId}/attachments
Creates an attachment and adds it to an existing work order
ResourceOwnerWorkOrder_CreateAttachment 1 param body → 200201403500
PUT
/v1/resourceowner/workorders/{workOrderId}/status
Update status of a work order
ResourceOwnerWorkOrder_UpdateWorkOrderStatus 1 param body → 200403500
GET
/v1/resourceowner/workorders/articles
Get all articles
ResourceOwnerWorkOrder_GetArticleList → 200403500
POST
/v1/resourceowner/workorders/articles
Create a article
ResourceOwnerWorkOrder_CreateArticle body → 200201403500
GET
/v1/resourceowner/workorders/articles/{workOrderArticleId}
Get a specific article
ResourceOwnerWorkOrder_GetArticle 1 param → 200403500
PUT
/v1/resourceowner/workorders/articles/{workOrderArticleId}
Update a article
ResourceOwnerWorkOrder_UpdateArticle 1 param body → 200403500
DELETE
/v1/resourceowner/workorders/articles/{workOrderArticleId}
Delete a article
ResourceOwnerWorkOrder_DeleteArticle 1 param → 200403500
GET
/v1/resourceowner/workorders/categories
Get all categories
ResourceOwnerWorkOrder_GetCategoryList → 200403500
POST
/v1/resourceowner/workorders/categories
Create a category
ResourceOwnerWorkOrder_CreateCategory body → 200201403500
GET
/v1/resourceowner/workorders/categories/{workOrderCategoryId}
Get a specific category
ResourceOwnerWorkOrder_GetCategory 1 param → 200403500
DELETE
/v1/resourceowner/workorders/categories/{workOrderCategoryId}
Delete a category
ResourceOwnerWorkOrder_DeleteCategory 1 param → 200403500
GET
/v1/resourceowner/workorders/customers
Get all customers
ResourceOwnerWorkOrder_GetCustomerList → 200403500
POST
/v1/resourceowner/workorders/customers
Create a customer
ResourceOwnerWorkOrder_CreateCustomer body → 200201403500
GET
/v1/resourceowner/workorders/customers/{workOrderCustomerId}
Get a specific customer
ResourceOwnerWorkOrder_GetCustomer 1 param → 200403500
PUT
/v1/resourceowner/workorders/customers/{workOrderCustomerId}
Update a customer
ResourceOwnerWorkOrder_UpdateCustomer 1 param body → 200403500
DELETE
/v1/resourceowner/workorders/customers/{workOrderCustomerId}
Delete a customer
ResourceOwnerWorkOrder_DeleteCustomer 1 param → 200403500
GET
/v1/resourceowner/workorders/referenceId
Get a new reference id for a work order (not unique)
ResourceOwnerWorkOrder_GetNextWorkOrderId → 200403500

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are WorkOrderModelGET (28 properties), WorkOrderModelSyncPUT (23 properties), WorkOrderModelPUT (22 properties), WorkOrderModelPOST (22 properties). Each schema is shown below with its type and property counts.

WorkOrderCategoryModelGET
object
3 properties 1 required
WorkOrderAttachmentModelPOST
object
3 properties 2 required
WorkOrderItemModelPOST
object
8 properties 2 required
WorkOrderStatusHistoryModelGET
object
3 properties
WorkOrderArticleModelPOST
object
4 properties 3 required
WorkOrderCustomerModelPOST
object
7 properties
WorkOrderArticleModelGET
object
7 properties 3 required
WorkOrderNoteModelPOST
object
1 property 1 required
WorkOrderNoteModelGET
object
4 properties 1 required
WorkOrderArticleModelPUT
object
4 properties 3 required
CustomerBillingAddressModel
object
8 properties
PositionPointModel
object
2 properties
WorkOrderItemModelGET
object
11 properties 2 required
WorkOrderCustomerModelGET
object
9 properties
WorkOrderCategoryModelPOST
object
1 property 1 required
WorkOrderModelPUT
object
22 properties
WorkOrderAttachmentModelGET
object
6 properties 2 required
WorkOrderAttachmentModelPUT
object
4 properties 2 required
WorkOrderCustomerModelPUT
object
7 properties
WorkOrderModelSyncPUT
object
23 properties
CustomerJobAddressModel
object
8 properties
WorkOrderModelGET
object
28 properties
WorkOrderItemModelPUT
object
9 properties 2 required
WorkOrderNoteModelPUT
object
2 properties 1 required
TimeSpan
object
15 properties
WorkOrderModelPOST
object
22 properties
WorkOrderStatusModelPUT
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

automile-resourceownerworkorder-api-openapi.yml Raw ↑

Other APIs Automile publishes across the network.

Automile ClientApi API
Automile ClientApiAuthorizations API
Automile ClientContracts API
Automile ClientCustom API
Automile ClientOnboarding API
Automile ClientOrder API
Automile ClientTextMessage API
Automile ClientUsers API
Automile Echo API
Automile Home API
Automile Login API
Automile OAuth API
Where this information came from

This is an independent, third-party profile of Automile ResourceOwnerWorkOrder API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.