Skip to main content

Schema introspection

Every command below with arguments supports two read-only flags for tooling and AI agents:
  • --show-file-schema: print the JSON Schema for the full request object (the format --filename accepts).
  • --show-argument-schema <flag-name>: print the JSON Schema for one argument’s value. Pass the kebab flag name without the leading -- (e.g. project-id, not --project-id).
Both write pure JSON to stdout and never call the API. They cannot be combined with any other command-specific flag.

create

Create a new event Create a new event (span) within a session trace. The request body is a bare event object (no event wrapper). Required properties:
  • event_type (string): Must be one of: chain, model, tool, session.
  • inputs (object): Input data for the event.
Auto-generated properties (provided by the server when omitted):
  • event_id (string, UUID): Unique identifier for the event.
  • session_id (string, UUID): Session/trace identifier.
  • parent_id (string, UUID): Parent event ID. Defaults to session_id.
Optional properties with defaults:
  • event_name (string): Name of the event. Defaults to "unknown".
  • source (string): Source of the event (e.g. sdk-python). Defaults to "unknown".
Optional properties:
  • config (object): Configuration data (e.g. model parameters, prompt templates).
  • outputs (object): Output data from the event.
  • error (string or null): Error message if the event failed.
  • children_ids (array of strings): IDs of child events.
  • duration (number): Duration of the event in milliseconds.
  • start_time (number): Unix timestamp in milliseconds for event start.
  • end_time (number): Unix timestamp in milliseconds for event end.
  • metadata (object): Additional metadata (e.g. token counts, cost).
  • metrics (object): Custom metrics.
  • feedback (object): Feedback data (e.g. ratings, ground truth).
  • user_properties (object): User properties associated with the event.

Usage

Options

FlagTypeRequiredDescription
--event-typestringyesType of event (model, tool, chain, or session) Allowed: model, tool, chain, session.
--inputsjsonyesInput data for the event
--children-idsjsonnoChild event IDs in the trace hierarchy
--configjsonnoConfiguration used for this event
--durationnumbernoEvent duration in milliseconds
--end-timenumbernoEvent end time as Unix milliseconds
--errorstringnoError message if the event failed
--event-idstringnoUnique event identifier
--event-namestringnoName of the event
--feedbackjsonnoFeedback data associated with the event
--metadatajsonnoArbitrary metadata for the event
--metricsjsonnoMetric values computed for the event
--outputsjsonnoOutput data from the event
--parent-idstringnoParent event ID in the trace hierarchy
--project-idstringnoProject ID
--session-idstringnoSession this event belongs to
--sourcestringnoSource of the event (e.g., sdk-python)
--start-timenumbernoEvent start time as Unix milliseconds
--user-propertiesjsonnoUser properties associated with the event
Also supports --show-file-schema, --show-argument-schema <flag-name>, and --filename. See Schema introspection for details.

Example response

get

Get an event by ID Retrieve a single event by its unique identifier. The event is fetched directly from S3/MinIO storage.

Usage

Options

FlagTypeRequiredDescription
--event-idstringyesThe unique identifier of the event to retrieve
Also supports --show-file-schema, --show-argument-schema <flag-name>, and --filename. See Schema introspection for details.

update

Update an event Update fields on an existing event. Only the provided fields are modified; omitted fields are left unchanged. Extra fields not listed below are accepted by the server but silently ignored.

Usage

Options

FlagTypeRequiredDescription
--event-idstringyesThe unique identifier of the event to update
--children-idsjsonnoIDs of child events to set (must be non-empty; an empty array is ignored)
--configjsonnoConfiguration fields to merge into the event
--durationnumbernoEvent duration in milliseconds
--end-timenumbernoUnix timestamp in milliseconds for event end
--feedbackjsonnoFeedback fields to merge into the event
--metadatajsonnoMetadata fields to merge into the event
--metricsjsonnoMetric values to merge into the event
--outputsjsonnoOutput object to replace on the event. Must be an object or null; null preserves the existing outputs. Non-object values (strings, arrays, scalars) are rejected.
--user-propertiesjsonnoUser properties to merge into the event
Also supports --show-file-schema, --show-argument-schema <flag-name>, and --filename. See Schema introspection for details.

Example request

Retrieve events based on filters Search events via POST with filtering and pagination. This is the primary method for retrieving events from HoneyHive.

Usage

Options

FlagTypeRequiredDescription
--date-rangejsonnodateRange
--evaluation-idstringnoFilter by evaluation/experiment run ID
--filtersjsonnofilters
--ignore-order / --no-ignore-orderbooleannoDeprecated: accepted but ignored. Results are always ordered by start_time descending.
--limitnumbernoLimit number of results (default 1000, max 1000)
--pagenumbernoPage number of results (default 1)
Also supports --show-file-schema, --show-argument-schema <flag-name>, and --filename. See Schema introspection for details.

create-batch

Create a batch of events Create multiple events in a single request. When single_session is true, all events share the same session created from session_properties. Required properties:
  • events (array of event objects): Each event must include event_type (one of chain, model, tool, session) and inputs.
Optional properties:
  • single_session (boolean): If true, all events share a single session created from session_properties. Defaults to false.
  • session_properties (object): Session metadata used when single_session is true. May include session_name, start_time, metadata.
Unknown top-level fields and per-event fields are rejected at the SDK boundary; the legacy aliases is_single_session, session, and per-event project are no longer accepted.

Usage

Options

FlagTypeRequiredDescription
--eventsjsonyesArray of events to create
--session-propertiesjsonnoSession properties for batch event creation
--single-session / --no-single-sessionbooleannoIf true, all events share the same session
Also supports --show-file-schema, --show-argument-schema <flag-name>, and --filename. See Schema introspection for details.

Example response