Humanloop Documentation and API Reference

Log to a Tool.

You can use query parameters version_id, or environment, to target an existing version of the Tool. Otherwise the default deployed version will be chosen.

Instead of targeting an existing version explicitly, you can instead pass in Tool details in the request body. In this case, we will check if the details correspond to an existing version of the Tool, if not we will create a new version. This is helpful in the case where you are storing or deriving your Tool details in code.

Query parameters

version_idstringOptional

A specific Version ID of the Tool to log to.

environmentstringOptional

Name of the Environment identifying a deployed version to log to.

Request

This endpoint expects an object.

pathstringOptional

Path of the Tool, including the name. This locates the Tool in the Humanloop filesystem and is used as as a unique identifier. For example: folder/name or just name.

idstringOptional

ID for an existing Tool.

start_timedatetimeOptional

When the logged event started.

end_timedatetimeOptional

When the logged event ended.

outputstringOptional

Generated output from your model for the provided inputs. Can be None if logging an error, or if creating a parent Log with the intention to populate it later.

created_atdatetimeOptional

User defined timestamp for when the log was created.

errorstringOptional

Error message if the log is an error.

provider_latencydoubleOptional

Duration of the logged event in seconds.

stdoutstringOptional

Captured log and debug statements.

provider_requestmap from strings to anyOptional

Raw request sent to provider.

provider_responsemap from strings to anyOptional

Raw response received the provider.

inputsmap from strings to anyOptional

The inputs passed to the prompt template.

sourcestringOptional

Identifies where the model was called from.

metadatamap from strings to anyOptional

Any additional metadata to record.

source_datapoint_idstringOptional

Unique identifier for the Datapoint that this Log is derived from. This can be used by Humanloop to associate Logs to Evaluations. If provided, Humanloop will automatically associate this Log to Evaluations that require a Log for this Datapoint-Version pair.

trace_parent_idstringOptional

The ID of the parent Log to nest this Log under in a Trace.

userstringOptional

End-user ID related to the Log.

environmentstringOptional

The name of the Environment the Log is associated to.

savebooleanOptional

Whether the request/response payloads will be stored on Humanloop.

log_idstringOptional

This will identify a Log. If you don’t provide a Log ID, Humanloop will generate one for you.

toolobjectOptional

Details of your Tool. A new Tool version will be created if the provided details are new.

Response

Successful Response

idstring

String ID of log.

tool_idstring

ID of the Tool the log belongs to.

version_idstring

ID of the specific version of the Tool.

session_idstringOptional

String ID of session the log belongs to.

1	curl -X POST https://api.humanloop.com/v5/tools/log \
2	-H "X-API-KEY: <apiKey>" \
3	-H "Content-Type: application/json" \
4	-d '{
5	"path": "math-tool",
6	"output": "35",
7	"inputs": {
8	"a": 5,
9	"b": 7
10	},
11	"tool": {
12	"function": {
13	"name": "multiply",
14	"description": "Multiply two numbers",
15	"parameters": {
16	"type": "object",
17	"properties": {
18	"a": {
19	"type": "number"
20	},
21	"b": {
22	"type": "number"
23	}
24	},
25	"required": [
26	"a",
27	"b"
28	]
29	}
30	}
31	}
32	}'

1	{
2	"id": "data_abc123",
3	"tool_id": "tl_def456",
4	"version_id": "tv_ghi789",
5	"session_id": "sesh_hw012"
6	}

Query parameters

Request

Response

Errors