https://api.demo.cula.earth/tracking/v1
All requests require an Authorization: Bearer <access_token> header and a Cula-Organisation-Id header.
Get your credentials
OAuth2 client credentials (
client_id and client_secret) are issued by the Cula team. Each credential set identifies your consumer and determines which organisations you can access. Contact your Cula representative to obtain credentials.Once you have them, export them for the examples below:Get an access token
Exchange your credentials for a short-lived access token:Extract the See authentication for details on token lifecycle and credential rotation.
access_token from the response and export it:Discover your config
Configs define which data points a resource expects. List your available material sourcing configs:Pick the config relevant to your process and inspect a specific version to see the expected data points:The response includes
data_point_configs, which lists each field you can submit: ID, type, unit, and constraints.Create a material sourcing step
Submit a new material sourcing record with your data points:A successful response returns
201 Created with the full resource including a server-generated id.Read back the resource
Retrieve the resource by server ID or by external ID prefixed with In the response, each data point includes:
ext-:input_value— the value you submitted.result_value— the server-normalised value (e.g. unit conversion, evaluation output).
output_containers[].contents[] array shows material contents computed from your output data points.Next steps
- Read resource identity for TypeIDs, external IDs, and references.
- Read data points for units, computed values, and validation.
- Browse the API reference for all endpoints.