Select the tab
ESET Inspect On-Prem – Table of Contents

POST Get basic process information

Relative path: /api/v1/epxprocesses

Request body

Display Schema instead of an Example or vice-versa

Type

Required

Example

Schema

application/json

Yes

 
{
  "process_id": "string",
  "device_id": "string"
}
 
{
  "$ref": "EPXProcessRequestSchema",
  "process_id": {
    "type": "string"
  },
  "device_id": {
    "type": "string"
  }
}

Responses

Display Schema+Headers instead of an Example or vice-versa

Code

Description and Example

Description, Schema and Headers

200

OK


Response example

{
  "id": 0,
  "systemProcessId": 0,
  "moduleId": 0,
  "moduleUuid": "string",
  "commandLine": "string",
  "user": "string",
  "uuid": "string"
}

OK


Response schema

{
  "$ref": "GetProcessResponseSchema",
  "id": {
    "type": "integer"
  },
  "systemProcessId": {
    "type": "integer"
  },
  "moduleId": {
    "type": "integer"
  },
  "moduleUuid": {
    "type": "string",
    "format": "uuid"
  },
  "commandLine": {
    "type": "string"
  },
  "user": {
    "type": "string"
  },
  "uuid": {
    "type": "string",
    "format": "uuid"
  }
}


Headers

{
  "X-Security-Token": {
    "$ref": "X-Security-Token",
    "description": "Authentication token",
    "schema": {
      "$ref": "AuthenticateTokenResponse",
      "type": "string",
      "example": "eyJhbGciOi[..]ziJSUGusY5kAI"
    }
  }
}

404

Specified element was not found

Specified element was not found


Response schema

{
  "$ref": "NotFoundResponse",
  "description": "Specified element was not found"
}