Armor JSM - Service Requests API

openapi: 3.2.0
info:
  title: MDR Public JSM - Service Requests API
  version: 1.0.0
  description: 'Comprehensive API documentation for Armor''s Managed Detection and Response (MDR) platform.


    This unified API provides access to:


    ## AI Platform (AIP)

    - AI-processed incident analysis with threat indicators and recommendations

    - Entity threat intelligence for security entities associated with incidents


    ## Microsoft Defender Integration

    - Machine/device management in Microsoft Defender for Endpoint

    - Security action execution (isolation, scans, investigations)

    - Investigation package collection and live response operations


    ## Detection Rules Management

    - Microsoft Sentinel detection rules across customer environments

    - Enriched rule metadata including MITRE ATT&CK mappings

    - Incident generation statistics


    ## JSM Middleware

    - Security incident management and tracking

    - Metrics aggregation and reporting

    - Service request management

    - Organization management


    ## Monthly Security Reports

    - Access to monthly security reports (PowerPoint, JSON, PDF)

    - Security metrics and performance indicators

    - Data ingestion analytics


    ## Threat Intelligence

    - Threat actor intelligence data

    - Customer-specific threat intelligence based on deployed products

    - OpenCTI GraphQL proxy for advanced queries


    ## Authentication

    All endpoints (except health checks) require OAuth2 Bearer token authentication.


    For authentication details, see: https://kb.armor.com/kb/sso-authentication-with-postman

    '
  contact:
    name: Armor Security Team
    url: https://armor.com
servers:
- url: https://mdr.api.secure-prod.services
  description: Production environment
- url: https://mdr.api.secure-dev.services
  description: Development environment
security:
- OAuth2BearerAuth: []
- FH-AUTH: []
tags:
- name: JSM - Service Requests
  description: Service request management
paths:
  /service-requests:
    get:
      tags:
      - JSM - Service Requests
      summary: List service requests
      description: 'Retrieve a paginated list of service requests from JSM with filtering and sorting options.

        '
      operationId: listServiceRequests
      parameters:
      - name: sortBy
        in: query
        description: Field to sort by
        schema:
          type: string
          enum:
          - id
          - status
          - summary
          - priority
          - severity
          - updated
          - created
          default: id
      - name: sortDirection
        in: query
        description: Sort direction
        schema:
          type: string
          enum:
          - asc
          - desc
          default: desc
      - name: textSearch
        in: query
        description: Text search query
        schema:
          type: string
      - name: startAt
        in: query
        description: Pagination start index
        schema:
          type: integer
          minimum: 0
          default: 0
      - name: pageSize
        in: query
        description: Number of items per page
        schema:
          type: integer
          minimum: 1
          maximum: 100
          default: 20
      - name: status
        in: query
        description: Comma-separated list of statuses
        schema:
          type: string
      - name: priority
        in: query
        description: Comma-separated list of priority levels
        schema:
          type: string
      - name: organization
        in: query
        description: Comma-separated list of organization IDs
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved service requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceRequestListResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No organizations found
          content:
            text/plain:
              schema:
                type: string
components:
  schemas:
    Error:
      type: object
      properties:
        message:
          type: string
    ServiceRequestListItem:
      type: object
      properties:
        id:
          type: string
        summary:
          type: string
        status:
          type: string
        priority:
          type: string
        created:
          type: string
          format: date-time
        updated:
          type: string
          format: date-time
        assignee:
          type:
          - string
          - 'null'
        orgs:
          type: array
          items:
            type: object
            properties:
              orgId:
                type: string
              orgName:
                type: string
    ServiceRequestListResponse:
      type: object
      properties:
        totalRows:
          type: integer
        issues:
          type: array
          items:
            $ref: '#/components/schemas/ServiceRequestListItem'
        approvedOrgs:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              name:
                type: string
  securitySchemes:
    OAuth2BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: OAuth2
      description: 'OAuth2 Scoped Access Token authentication. An authorization header with Bearer token

        must be included with every authenticated request.


        For authentication details, see the official documentation:

        https://kb.armor.com/kb/sso-authentication-with-postman

        '
    FH-AUTH:
      type: http
      scheme: bearer
      bearerFormat: FH-AUTH
      description: 'FH-AUTH token authentication.


        ## Authentication Flow


        1. **Authorize**: POST credentials to `/auth/authorize` to receive an authorization code

        2. **Token Exchange**: Exchange the code at `/auth/token` within 2 minutes for access tokens

        3. **API Calls**: Use the access token in the `Authorization: FH-AUTH {token}` header

        4. **Refresh**: When token expires (15 minutes), refresh via `/auth/token/reissue`


        ## Security Notes


        - Authorization codes expire in 2 minutes

        - Access tokens expire in 15 minutes

        - All endpoints require HTTPS

        - Never log or persist tokens in plain text


        Include the access token in the Authorization header:

        ```

        Authorization: FH-AUTH {access_token}

        ```

        '