Example: A Session creating an outline for a book about space
Add Session Headers
Structure Your Paths
Make Your Request
Header | Type | Description | Default | Example |
---|---|---|---|---|
Helicone-Session-Id | string | Unique identifier for the session (recommend UUID) | N/A | "550e8400-e29b-41d4-a716-446655440000" |
Helicone-Session-Path | string | Path representing the trace hierarchy using / syntax | N/A | "/abstract" or "/parent/child" |
Helicone-Session-Name | string | Human-readable name for the session | N/A | "Course Plan" |
Session ID Guidelines
Path Structure Best Practices
550e8400-e29b-41d4-a716-446655440000
user_123_conversation_456
/
(forward slash)/
to separate levels: /parent/child/grandchild
/analyze_request/fetch_data/process_results
"Customer Support"
- All support sessions use this name"Content Generation"
- All content creation sessions use this name"Trip Planning Agent"
- All trip planning workflows use this nameNeed more help?