Skip to main content
POST
Import machine data

Authorizations

Authorization
string
header
required

OAuth 2.0 client credentials. Exchange your client_id and client_secret for an access token scoped to the organisation that provides data access.

Headers

Cula-Organisation-Id
string
required

ID of the organisation the request operates on behalf of (e.g. org_...). Must be an organisation the API client has access to.

Example:

"org_01k83mfmhgchya944v86ryvhpq"

Body

application/json
type
enum<string>
required

Import mode. Only sync is currently supported.

Available options:
sync
Example:

"sync"

items
object[]
required

Machine data items to ingest. Between 1 and 200 items per request.

Required array length: 1 - 200 elements
external_id
string

A optional custom ID that can be set to an internal ID from your system. This ID must be unique within all objects of the organisation you operate in. You can later use this external ID to reference and query this object. Be aware that you can update this ID later. If you need an immutable ID, use the object ID returned when creating the object.

Required string length: 1 - 100
Pattern: ^[A-Za-z0-9\-_]+$
Example:

"MY-IMPORT-ID"

Response

The machine data items were ingested successfully.

id
string
required

Unique identifier of the machine data import.

Example:

"mdi_01knwph011nqfnv5frjh3e32wq"

type
enum<string>
required

Import mode the request was processed with.

Available options:
sync
Example:

"sync"

item_count
number
required

Number of machine data items in the import.

Example:

1

external_id
string | null
required

The external ID you assigned to this import (if any).

Example:

"MY-IMPORT-ID"

created_at
string<date-time>
required

When the import was recorded.

Example:

"2025-10-25T13:02:52.932Z"