Skip to main content
GET
/
machine-data-point-configs
/
{id}
Get a machine data point config
curl --request GET \
  --url https://api.demo.cula.earth/tracking/v1/machine-data-point-configs/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Cula-Organisation-Id: <cula-organisation-id>'
{
  "id": "mdp_01kqzcjrpyf27tge9dnvsqv8t2",
  "external_id": "GC-RETENTATE-FLOW",
  "name": "retentate outlet flow rate",
  "unit": "m3/h",
  "factor": 1,
  "site": {
    "id": "ste_01kqzcjrpyf27tge6smsbnhkh5",
    "external_id": "GC-SITE-REFINERY"
  },
  "machine": {
    "id": "mch_01kqzcjrpyf27tge77evmjmnqw",
    "external_id": "GC-RAWGAS-UPGRADE"
  },
  "measurement": {
    "id": "msr_01kqzcjrpyf27tge77evmjmnqw",
    "external_id": "GC-RAWGAS-FLOW"
  }
}

Authorizations

​
Authorization
string
header
required

OAuth2 client credentials flow. Exchange your client_id and client_secret for a short-lived access token, then pass it as a Bearer token in the Authorization header.

Headers

​
Cula-Organisation-Id
string
required

Organisation ID that scopes this request. The authenticated consumer must be authorized for this organisation. Omitting this header returns 400; passing an unauthorised org returns 403.

Path Parameters

​
id
string
required

Cula-assigned resource ID in TypeID format (e.g. stp_01kqzcjrpxf27tge33jwvjhkff). Alternatively, pass your external ID prefixed with ext- (e.g. ext-MY-STEP-001). The ext- prefix is unambiguous because TypeIDs use _ separators and never start with ext-.

Response

Machine data point config details.

​
id
string
required
Example:

"mdp_01kqzcjrpyf27tge9dnvsqv8t2"

​
name
string
required
Example:

"retentate outlet flow rate"

​
unit
string
required
Example:

"m3/h"

​
site
object
required

The site this data point config belongs to.

​
machine
object
required

The machine this data point config belongs to.

​
measurement
object
required

The measurement group this data point config belongs to.

​
factor
number

Multiplication factor applied to raw values.

Example:

1