openapi: 3.2.0 info: version: 0.48.24 termsOfService: https://www.decisiv.com/terms-of-use contact: name: Decisiv Support email: support@decisiv.com url: https://www.decisiv.com title: Asset Management Case Recipients API description: Inside of **Decisiv SRM Gateway**, the `Asset Management` module represents all interactions and functionality which an Account registered with a `Fleet subscription` can perform through an API interface. license: name: Proprietary identifier: proprietary url: https://www.decisiv.com/terms-of-use/ servers: - url: https://srm-api.staging.decisivapps.com - url: https://srm-api.decisivapps.com security: - OAuth2AuthorizationCode: [] AccessToken: [] - OAuth2Password: [] AccessToken: [] tags: - name: Case Recipients paths: /asset_management/{srm_account_id}/v1/cases/{case_id}/recipients: get: operationId: listCaseRecipients description: Lists all recipients associated with the requested case. summary: List all recipients for the requested case tags: - Case Recipients parameters: - name: srm_account_id in: path description: The account ID for SRM required: true schema: type: string - name: case_id in: path description: The case ID required: true schema: type: string - name: page[number] in: query required: false schema: type: number description: Sets the desired `page` when encountering larger result sets - name: page[size] in: query required: false schema: type: number description: Sets the desired maximum number of results per page responses: '200': description: Returns list of recipients content: application/vnd.api+json: example: data: - id: 20ff667d-582b-450c-a9cb-0b4662761543 type: users attributes: username: some@email.com first_name: Someone last_name: Somebody name: Someone Somebody email: other@email.com affiliation: account_name: Dealer Name recipient_type: other schema: $ref: '#/components/schemas/recipients' '400': description: This response may occur when an invalid request has been provided to the server. The request may be corrected by the consumer and resubmitted. content: application/vnd.api+json: example: errors: - title: Filter not allowed detail: '''{{filter_name}}'' is not allowed. Valid filters: {{filters_list}}' code: decisiv:filters:001 status: '400' source: parameter: filter[filter_name] schema: $ref: '#/components/schemas/errors_response' '401': description: This response may occur when the access token provided within the Authorization token has expired. content: application/vnd.api+json: example: errors: - title: Access unauthorized detail: Access unauthorized code: decisiv::access_token:001 status: '401' schema: $ref: '#/components/schemas/errors_response' '403': description: This response may occur when the authenticated user embedded within the Authorization header does not have access to the requested resource. content: application/vnd.api+json: example: errors: - title: Forbidden detail: User does not have permission to perform this action on the requested resource(s) code: decisiv:access:001 status: '403' schema: $ref: '#/components/schemas/errors_response' '404': description: This response may occur when the requested resource is not found. content: application/vnd.api+json: example: errors: - status: '404' code: decisiv:resource:001 title: Resource Identifier - Not Found detail: The parent resource could not be found source: parameter: id schema: $ref: '#/components/schemas/errors_response' '424': description: This response may occur when there is an unresolved data dependency or configuration required inside of the Decisiv Platform preventing access to the requested action. content: application/vnd.api+json: example: errors: - title: Failed Dependency detail: Failed Dependency code: '424' status: '424' schema: $ref: '#/components/schemas/errors_response' '504': description: This response may occur when there is an unexpected system timeout. content: application/vnd.api+json: example: errors: - code: '504' detail: Gateway timeout error status: '504' title: Gateway timeout error schema: $ref: '#/components/schemas/errors_response' /asset_management/{srm_account_id}/v1/cases/{case_id}/recipients/{id}: get: operationId: getCaseRecipient description: Retrieves a specific recipient associated with the requested case. summary: Get a recipient for the requested case tags: - Case Recipients parameters: - name: srm_account_id in: path description: The account ID for SRM required: true schema: type: string - name: case_id in: path description: The case ID required: true schema: type: string - name: id in: path description: The resource uuid required: true schema: type: string responses: '200': description: Returns list of recipient content: application/vnd.api+json: example: data: id: 20ff667d-582b-450c-a9cb-0b4662761543 type: users attributes: username: some@email.com first_name: Someone last_name: Somebody name: Someone Somebody email: other@email.com affiliation: account_name: Dealer Name recipient_type: other schema: $ref: '#/components/schemas/recipient' '401': description: This response may occur when the access token provided within the Authorization token has expired. content: application/vnd.api+json: example: errors: - title: Access unauthorized detail: Access unauthorized code: decisiv::access_token:001 status: '401' schema: $ref: '#/components/schemas/errors_response' '403': description: This response may occur when the authenticated user embedded within the Authorization header does not have access to the requested resource. content: application/vnd.api+json: example: errors: - title: Forbidden detail: User does not have permission to perform this action on the requested resource(s) code: decisiv:access:001 status: '403' schema: $ref: '#/components/schemas/errors_response' '404': description: This response may occur when the requested resource is not found. content: application/vnd.api+json: example: errors: - status: '404' code: decisiv:resource:001 title: Resource Identifier - Not Found detail: The parent resource could not be found source: parameter: id schema: $ref: '#/components/schemas/errors_response' '424': description: This response may occur when there is an unresolved data dependency or configuration required inside of the Decisiv Platform preventing access to the requested action. content: application/vnd.api+json: example: errors: - title: Failed Dependency detail: Failed Dependency code: '424' status: '424' schema: $ref: '#/components/schemas/errors_response' '504': description: This response may occur when there is an unexpected system timeout. content: application/vnd.api+json: example: errors: - code: '504' detail: Gateway timeout error status: '504' title: Gateway timeout error schema: $ref: '#/components/schemas/errors_response' components: schemas: recipients: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/recipient_properties-data' meta: type: object error_response: type: object properties: status: type: string title: type: string detail: type: - string - 'null' code: type: - string - 'null' source: type: object properties: parameter: type: - string - 'null' pointer: type: - string - 'null' links: type: object description: Links related to this error (e.g. documentation reference). additionalProperties: type: string format: uri required: - status - title recipient: type: object required: - data properties: data: type: object properties: id: type: string format: uuid type: type: string attributes: type: object properties: username: type: string description: The username inside the system example: support@support.com first_name: type: string description: First name example: John last_name: type: string description: Last name example: Doe name: type: string description: Full name example: John Doe email: type: string description: Contact email example: support@support.com affiliation: type: object properties: account_name: type: string description: The account from the recipient example: Dealer Name recipient_type: type: string example: other required: - attributes - type - id recipient_properties-data: type: object properties: id: type: string format: uuid type: type: string attributes: type: object properties: username: type: string description: The username inside the system example: support@support.com first_name: type: string description: First name example: John last_name: type: string description: Last name example: Doe name: type: string description: Full name example: John Doe email: type: string description: Contact email example: support@support.com affiliation: type: object properties: account_name: type: string description: The account from the recipient example: Dealer Name recipient_type: type: string example: other required: - attributes - type - id errors_response: type: object properties: errors: type: array items: $ref: '#/components/schemas/error_response' required: - errors securitySchemes: AccessToken: type: http scheme: bearer bearerFormat: JWT OAuth2AuthorizationCode: type: oauth2 description: OAuth 2.0 Authorization Code flow. This is the required flow for new integrations. See https://api-docs.decisiv.net/docs/api/oauth/ flows: authorizationCode: authorizationUrl: https://login.decisiv.net/auth/api_gateway tokenUrl: https://login.decisiv.net/oauth/token refreshUrl: https://login.decisiv.net/oauth/token scopes: {} OAuth2Password: type: oauth2 description: '**Deprecated.** OAuth 2.0 Password flow. New integrations must use the Authorization Code flow (`OAuth2AuthorizationCode`); this flow remains available only during the migration window and will be removed in a future release. See https://api-docs.decisiv.net/docs/api/oauth/' flows: password: tokenUrl: https://login.decisiv.net/oauth/token scopes: {}