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

Decisiv VMRS API

The VMRS API from Decisiv — 18 operation(s) for vmrs.

Decisiv VMRS API is one of 70 APIs that Decisiv publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 18 operations across 18 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 0.48.24.

Requests are made against 2 base URLs: https://srm-api.staging.decisivapps.com, https://srm-api.decisivapps.com.

18 operations 18 paths 20 schemas 18 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.48.24
Base URL
https://srm-api.decisivapps.com
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 3

Decisiv VMRS API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (AccessToken). It supports OAuth 2.0 (OAuth2AuthorizationCode) using the authorizationCode flow. It supports OAuth 2.0 (OAuth2Password) using the password flow. By default, every request must be authenticated.

  • OAuth2AuthorizationCode — OAuth 2.0 Authorization Code flow. This is the required flow for new integrations. See https://api-docs.decisiv.net/docs/api/oauth/
  • OAuth2Password — Deprecated. OAuth 2.0 Password flow. New integrations must use the Authorization Code flow (OAuth2AuthorizationCode); this flow remains available only during t…

Paths & Operations 18

Across 18 paths, the API surfaces 18 operations — 18 GET. Each is listed below with its method, path, parameters, and response codes.

VMRS 18
GET
/asset_management/{srm_account_id}/v1/vmrs/asset_types
List all VMRS Asset Types (Code Key 2)
listVmrsAssetTypes 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/reasons_for_repair
List all VMRS Reasons for Repair (Code Key 14)
listVmrsReasonsForRepair 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/repair_priorities
List all VMRS Repair Priorities (Code Key 16)
listVmrsRepairPriorities 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/repair_sites
List all VMRS Repair Sites (Code Key 17)
listVmrsRepairSites 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/components
List all VMRS Components (Code Key 33)
listVmrsComponents 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/operator_reports
List all VMRS Operator Reports (Code Key 82)
listVmrsOperatorReports 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/positions
List all VMRS Positions (Code Key 79)
listVmrsPositions 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/work_accomplished
List all VMRS Work Accomplished values (Code Key 15)
listVmrsWorkAccomplished 3 params → 200401403404428504
GET
/asset_management/{srm_account_id}/v1/vmrs/technician_part_failure_codes
List all VMRS Technician Part Failure Codes (Code Key 18)
listVmrsTechnicianPartFailureCodes 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/asset_types
List all VMRS Asset Types (Code Key 2)
listVmrsAssetTypes 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/reasons_for_repair
List all VMRS Reasons for Repair (Code Key 14)
listVmrsReasonsForRepair 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/repair_priorities
List all VMRS Repair Priorities (Code Key 16)
listVmrsRepairPriorities 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/repair_sites
List all VMRS Repair Sites (Code Key 17)
listVmrsRepairSites 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/components
List all VMRS Components (Code Key 33)
listVmrsComponents 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/operator_reports
List all VMRS Operator Reports (Code Key 82)
listVmrsOperatorReports 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/positions
List all VMRS Positions (Code Key 79)
listVmrsPositions 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/work_accomplished
List all VMRS Work Accomplished values (Code Key 15)
listVmrsWorkAccomplished 3 params → 200401403404428504
GET
/service_management/{srm_account_id}/v1/vmrs/technician_part_failure_codes
List all VMRS Technician Part Failure Codes (Code Key 18)
listVmrsTechnicianPartFailureCodes 3 params → 200401403404428504

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are error_response (6 properties), vmrs_reason_for_repair_properties-data (3 properties), vmrs_position_properties-data (3 properties), vmrs_repair_site_properties-data (3 properties). Each schema is shown below with its type and property counts.

vmrs_technician_part_failure_codes
object
2 properties 1 required
vmrs_components
object
2 properties 1 required
error_response
object
6 properties 2 required
vmrs_repair_sites
object
2 properties 1 required
vmrs_asset_type_properties-data
object
3 properties 3 required
vmrs_component_properties-data
object
3 properties 3 required
errors_response
object
1 property 1 required
vmrs_technician_part_failure_code_properties-data
object
3 properties 3 required
vmrs_work_accomplished_list
object
2 properties 1 required
vmrs_operator_report_properties-data
object
3 properties 3 required
vmrs_work_accomplished_properties-data
object
3 properties 3 required
vmrs_repair_site_properties-data
object
3 properties 3 required
vmrs_asset_types
object
2 properties 1 required
vmrs_repair_priorities
object
2 properties 1 required
vmrs_position_properties-data
object
3 properties 3 required
vmrs_positions
object
2 properties 1 required
vmrs_reason_for_repair_properties-data
object
3 properties 3 required
vmrs_reasons_for_repair
object
2 properties 1 required
vmrs_operator_reports
object
2 properties 1 required
vmrs_repair_priority_properties-data
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

decisiv-vmrs-api-openapi.yml Raw ↑

Other APIs Decisiv publishes across the network.

Decisiv Platform API
Decisiv Account Roles API
Decisiv Account User Roles API
Decisiv Account Users API
Decisiv Accounts API
Decisiv Assets API
Decisiv Case Actions API
Decisiv Case Attachments API
Decisiv Case Line Item Internal Labels API
Decisiv Case Line Item Parts API
Decisiv Case Line Item Parts Relationships SalesPerson API
Decisiv Case Line Items - Additional Charges API
Where this information came from

This is an independent, third-party profile of Decisiv VMRS 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.