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

The ResourceOwnerContact3 API from Automile — 12 operation(s) for resourceownercontact3.

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

Tagged areas include ResourceOwnerContact3. 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 22 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 22 schemas 1 DELETE7 GET3 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 ResourceOwnerContact3 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, 7 GET, 3 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

ResourceOwnerContact3 15
GET
/v1/resourceowner/contacts3
Get a list of all contacts that user is associated with
GetResourceOwnerContacts3 → 200500
POST
/v1/resourceowner/contacts3
Creates a new contact
CreateResourceOwnerContact3 body → 200500403
GET
/v1/resourceowner/contacts3/{contactId}
Get a contact by id
GetResourceOwnerContact3 1 param → 200403404500
PUT
/v1/resourceowner/contacts3/{contactId}
Updates the given contact id
EditResourceOwnerContact3 1 param body → 200403404500
DELETE
/v1/resourceowner/contacts3/{contactId}
Removes the given contact
DeleteResourceOwnerContact3 1 param → 200403500400404
GET
/v1/resourceowner/contacts3/me
Get the contact representing myself
GetResourceOwnerContactMe3 → 200403404500
GET
/v1/resourceowner/contacts3/me/image
Get contact profile image
GetImage3 1 param → 200
POST
/v1/resourceowner/contacts3/me/uploadimage
Upload contact profile image
MeUploadImage3 body → 200406500
PUT
/v1/resourceowner/contacts3/me/removeimage
Removes the users profile image
MeRemoveImage3 → 200500
PUT
/v1/resourceowner/contacts3/me/updatedefaultvehicle/{vehicleId}
Updates the default vehicle
MeUpdateDefaultVehicle3 1 param → 200403500
PUT
/v1/resourceowner/contacts3/updatedefaultvehicle/{vehicleId}
Updates the default vehicle
UpdateResourceOwnerContactDefaultVehicle3 1 param → 200403500
POST
/v1/resourceowner/contacts3/customcategory
Add and remove custom categories
ResourceOwnerContact3CustomCategory body → 200500
GET
/v1/resourceowner/contacts3/{contactId}/customcategories/{customCategoryId}
Get a custom category
GetCustomCategoryResourceOwnerContacts3 2 params → 200500
GET
/v1/resourceowner/contacts3/{contactId}/customcategories
Get a all custom categories
GetCustomCategoriesResourceOwnerContacts3 1 param → 200500
GET
/v1/resourceowner/contacts3/getwebsocketauthenticationtoken
Get an encrypted token to be used for header authentication to Web Socket API. The response will also contain for how long the token is valid.
GetWebSocketAuthenticationToken → 200500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Contact3DetailModel (35 properties), OrganizationPermissionBooleans (26 properties), Contact3EditModel (17 properties), Contact3Model (16 properties). Each schema is shown below with its type and property counts.

TripScoreMessageModel
object
2 properties
CustomCategoryPostModel
object
3 properties
SSOConfigurationModel
object
3 properties
CompanyScopesModel
object
3 properties
TripScoreInformationModel
object
4 properties
HoursOfServiceSettingsModel
object
11 properties
CustomCategoryModel
object
3 properties
Contact3EditModel
object
17 properties
ProblemDetails
object
5 properties
ContactMenuLayoutModel
object
3 properties
Contact3Model
object
16 properties
AddressModel
object
10 properties 4 required
AccountOutstandingMessageModel
object
2 properties
TripScoreLevelModel
object
3 properties
CustomCategoryCreateModel
object
2 properties
Contact3DetailModel
object
35 properties
AccountInformationModel
object
1 property
OrganizationModel
object
10 properties
OrganizationPermissionBooleans
object
26 properties
Contact3CreateModel
object
15 properties 3 required
TimeSpan
object
15 properties
ContactWebSocketAuthenticationTokenModel
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

automile-resourceownercontact3-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 ResourceOwnerContact3 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.