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 ResourceOwnerContact2 API

The ResourceOwnerContact2 API from Automile — 12 operation(s) for resourceownercontact2.

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

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

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

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

15 operations 12 paths 15 schemas 1 DELETE6 GET4 POST4 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 ResourceOwnerContact2 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 15

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

ResourceOwnerContact2 15
GET
/v1/resourceowner/contacts2
Get a list of all contacts that user is associated with
GetResourceOwnerContacts2 → 200500
POST
/v1/resourceowner/contacts2
Creates a new contact
CreateResourceOwnerContact2 body → 200403500
GET
/v1/resourceowner/contacts2/{contactId}
Get a contact by id
GetResourceOwnerContact2 1 param → 200403404500
PUT
/v1/resourceowner/contacts2/{contactId}
Updates the given contact id
EditResourceOwnerContact2 1 param body → 200404403500
DELETE
/v1/resourceowner/contacts2/{contactId}
Removes the given contact
DeleteResourceOwnerContact2 1 param → 200403404500400
GET
/v1/resourceowner/contacts2/me
Get the contact representing myself
GetResourceOwnerContactMe2 → 200403404500
GET
/v1/resourceowner/contacts2/me/image
Get contact profile image
GetImage 1 param → 200
POST
/v1/resourceowner/contacts2/me/uploadimage
Upload contact profile image
MeUploadImage body → 200500406
PUT
/v1/resourceowner/contacts2/me/removeimage
Removes the users profile image"
MeRemoveImage → 200500
POST
/v1/resourceowner/contacts2/update-rfid
UpdateRfidResourceOwnerContact2 body → 200
PUT
/v1/resourceowner/contacts2/me/updatedefaultvehicle/{vehicleId}
Updates the default vehicle
MeUpdateDefaultVehicle2 1 param → 200403500
PUT
/v1/resourceowner/contacts2/updatedefaultvehicle/{vehicleId}
Updates the default vehicle
UpdateResourceOwnerContactDefaultVehicle2 1 param → 200403500
POST
/v1/resourceowner/contacts2/customcategory
Add and remove custom categories
ResourceOwnerContact2CustomCategory body → 200500
GET
/v1/resourceowner/contacts2/{contactId}/customcategories/{customCategoryId}
Get a custom category
GetCustomCategoryResourceOwnerContacts2 2 params → 200500
GET
/v1/resourceowner/contacts2/{contactId}/customcategories
Get a all custom categories
GetCustomCategoriesResourceOwnerContacts2 1 param → 200500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Contact2DetailModel (30 properties), Contact2EditModel (15 properties), TimeSpan (15 properties), Contact2Model (14 properties). Each schema is shown below with its type and property counts.

ContactMenuLayoutModel
object
3 properties
AddressModel
object
10 properties 4 required
CustomCategoryPostModel
object
3 properties
Contact2Model
object
14 properties
Contact2UpdateRfidModel
object
2 properties
Contact2DetailModel
object
30 properties
OrganizationModel
object
10 properties
Contact2CreateModel
object
13 properties 3 required
Contact2EditModel
object
15 properties
CompanyScopesModel
object
3 properties
TimeSpan
object
15 properties
HoursOfServiceSettingsModel
object
11 properties
CustomCategoryModel
object
3 properties
ProblemDetails
object
5 properties
CustomCategoryCreateModel
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

automile-resourceownercontact2-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 ResourceOwnerContact2 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.