OpenPipeline Ingest API - POST Custom generic event endpoint

Configures custom endpoints to ingest generic events.

The request consumes an application/json payload.

POSTSaaShttps://{your-environment-id}.live.dynatrace.com/platform/ingest/custom/events/{endpoint}

Authentication

To execute this request, you need an access token with openpipeline.events.custom scope.

To learn how to obtain and use it, see Tokens and authentication.

Parameters

Parameter
Type
Description
In
Required
endpoint
string

The configuration of the endpoint parameter.

path
required
body

The JSON body of the request. Contains the events for ingest.

body
required

Request body objects

The Events object

The events to be ingested.

Element
Type
Description
Required
<*>
object[]

List of events that will get ingested.

optional

Request body JSON model

This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.

[
  {
    "event.id": 1,
    "additionalProp1": "bar",
    "additionalProp2": "foo",
    "additionalProp3": [
      {
        "prop1": "string",
        "prop2": 1
      }
    ]
  },
  {
    "event.id": 2,
    "additionalProp1": 123.45,
    "additionalProp2": "lorem",
    "additionalProp3": [
      {
        "prop1": "string",
        "prop2": 1
      }
    ]
  }
]

Response

Response codes

Code
Type
Description
202
-

Accepted. Response doesn't have a body.

400

Failed. The input is invalid.

404

Failed. Endpoint not found.

413

Failed. Content too large.

429

Failed. Too many requests.

5XX

Server-side error.