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 SRM Gateway - Telematics

Ingest and read connected-asset telematics inside SRM: diagnostic readings and fault codes for registered assets, so a fault on a vehicle can open or enrich a service case at the point of service.

This API exposes 6 operations across 4 paths, organized into 2 resource areas, and defines 12 schemas. It is described by OpenAPI 3.1.0, at version 0.48.24.

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

6 operations 4 paths 12 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.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
2

Authentication & Security 3

Decisiv SRM Gateway - Telematics 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 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. They span 2 resource areas: Diagnostic Readings, Faults. Each is listed below with its method, path, parameters, and response codes.

Diagnostic Readings 3
GET
/telematics/{srm_account_id}/v1/diagnostic_readings
List all diagnostic readings for the requested account
listDiagnosticReadings 10 params → 200400401403404424504
POST
/telematics/{srm_account_id}/v1/diagnostic_readings
Create a new diagnostic reading
createDiagnosticReading 1 param body → 201400401403429
GET
/telematics/{srm_account_id}/v1/diagnostic_readings/{uuid}
Get details for a specific diagnostic reading
getDiagnosticReading 2 params → 200400401403404424504
Faults 3
GET
/telematics/{srm_account_id}/v1/faults
List all faults for the requested account
listFaults 1 param → 200400401403404424504
POST
/telematics/{srm_account_id}/v1/faults
Create a new fault
createFault 1 param body → 201400401403429
GET
/telematics/{srm_account_id}/v1/faults/{uuid}
Get details for a specific fault
getFault 2 params → 200400401403404424504

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are properties-attributes (11 properties), attributes (8 properties), error_response (6 properties), diagnostic_readings (2 properties). Each schema is shown below with its type and property counts.

error_response
object
6 properties 2 required
errors_response
object
1 property 1 required
relationship_object
object
1 property 1 required
relationship_objects
object
1 property 1 required
create_diagnostic_reading
object
1 property 1 required
create_fault
object
1 property 1 required
diagnostic_reading
object
1 property 1 required
diagnostic_readings
object
2 properties 1 required
fault
object
1 property 1 required
faults
object
2 properties 1 required
attributes
object
8 properties
properties-attributes
object
11 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

decisiv-telematics-openapi.yml Raw ↑
Where this information came from

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