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

The Contacts API from Decisiv — 4 operation(s) for contacts.

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

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

This API exposes 10 operations across 4 paths, and defines 13 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.

10 operations 4 paths 13 schemas 2 DELETE4 GET2 PATCH2 POST

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 Contacts 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 10

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

Contacts 10
GET
/asset_management/{srm_account_id}/v1/contacts
List all Contacts for the fleet
listContacts 6 params → 200400401403428504
POST
/asset_management/{srm_account_id}/v1/contacts
Create a Contact
createContact 1 param body → 201400401403404422504
GET
/asset_management/{srm_account_id}/v1/contacts/{id}
Retrieves a Contact from the requested Customer
getContact 3 params → 200400401403404428504
PATCH
/asset_management/{srm_account_id}/v1/contacts/{id}
Updates a Contact
updateContact 2 params body → 200400401403404422428504
DELETE
/asset_management/{srm_account_id}/v1/contacts/{id}
Deletes a Contact
deleteContact 2 params → 204401403404
GET
/service_management/{srm_account_id}/v1/customers/{customer_id}/contacts
List all Contacts for the requested Customer
8 params → 200400401403428504
POST
/service_management/{srm_account_id}/v1/customers/{customer_id}/contacts
Create a Contact
2 params body → 201400401403404422504
GET
/service_management/{srm_account_id}/v1/customers/{customer_id}/contacts/{id}
Retrieves a Contact from the requested Customer
3 params → 200400401403404428504
PATCH
/service_management/{srm_account_id}/v1/customers/{customer_id}/contacts/{id}
Updates Contact
3 params body → 200400401403404422428504
DELETE
/service_management/{srm_account_id}/v1/customers/{customer_id}/contacts/{id}
Deletes a Contact
3 params → 204401403404428

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are error_response (6 properties), contact_properties-data (4 properties), contact_properties-data_2 (4 properties), contacts (2 properties). Each schema is shown below with its type and property counts.

contact_by_id
object
1 property 1 required
contact_properties-data
object
4 properties 4 required
error_response
object
6 properties 2 required
contact
object
1 property 1 required
relationship_object
object
1 property 1 required
errors_response
object
1 property 1 required
contacts
object
2 properties 1 required
contact_by_id_2
object
1 property 1 required
contact_properties-data_2
object
4 properties 3 required
contact_2
object
1 property 1 required
contact_update
object
1 property 1 required
create_contact
object
1 property 1 required
contacts_2
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

decisiv-contacts-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 Contacts 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.