Event processing¶

POST {{baseUrl}}/api-versio.eventProcessing/1.0/environments/{{environment}}/events HTTP/1.1
Authorization: apiToken {{apiToken}}
Content-Type: application/json

[ // you can create more than one event with one request
  {
    "id": "1234", // optional: you can define your own event ID; the advantage of this is that you can overwrite the event at a later date, for example to update it
        "utc": 1722601661000 // optional: unix timestamp in milliseconds of the event. If empty, the time of receipt is used 
    "sourceType":"Qualys", // define the source on the basis of which the event exists; usually the application system (Qualys, Dynatrace, batch job)
    "trigger": "192.168.0.102", // which unit triggered the event (e.g. IP address or other ID or hostname)
    "externalIdLink":"http://qualys.com?id=EVENT-12345", // optional: external link for further information on the trigger
    "externalIdName":"Red Hat CVE detected", // optional: Descriptive name for the trigger
    "severity":4, // what is the severity of the event (values between 0-9)
    "classification":"Security vulnerability", // What context does the event have or to which group does the event belong (e.g. system access, security notice, hardware failure, malfunction, etc.)?
    "message":"Very long description text",
        "rawEvent": { // optional: anything you want to save
            "some":" cool information"
        }
  }
]