Skip to content

docs: add API reference for GET /v1/request/{requestId}/inputs#5576

Merged
chitalian merged 2 commits intomainfrom
docs/request-inputs-endpoint
Feb 17, 2026
Merged

docs: add API reference for GET /v1/request/{requestId}/inputs#5576
chitalian merged 2 commits intomainfrom
docs/request-inputs-endpoint

Conversation

@chitalian
Copy link
Contributor

Summary

Context

This endpoint lets users retrieve the prompt template inputs (variables) for a past request made through AI Gateway prompt management — enabling testing pipelines that replay requests against new prompt versions without storing inputs separately.

🤖 Generated with Claude Code

Documents the new endpoint that retrieves prompt template inputs
(variables) for a given request, enabling testing pipeline workflows
where users replay past requests against new prompt versions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 17, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
helicone Ready Ready Preview, Comment Feb 17, 2026 8:15pm
helicone-bifrost Ready Ready Preview, Comment Feb 17, 2026 8:15pm
helicone-eu Ready Ready Preview, Comment Feb 17, 2026 8:15pm

Request Review

@supabase
Copy link

supabase bot commented Feb 17, 2026

This pull request has been ignored for the connected project bolqqmqbrciybnypvklh because there are no changes detected in supbase/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@supabase
Copy link

supabase bot commented Feb 17, 2026

This pull request has been ignored for the connected project lmahfbbnchpworytrrqk because there are no changes detected in .supabase/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@claude
Copy link
Contributor

claude bot commented Feb 17, 2026

Claude finished @chitalian's task —— View job


PR Review Complete ✅

Score: 9/10 - Excellent documentation with clear structure and practical examples. Ready to merge.

Review Analysis

I've thoroughly reviewed this documentation PR for the new GET /v1/request/{requestId}/inputs endpoint. The changes include:

  1. New MDX documentation file (docs/rest/request/get-v1request-inputs.mdx)
  2. Navigation update in docs.json to add the page to the Request section

Strengths

Clear and comprehensive documentation structure

  • Well-organized sections: Overview, Use Cases, Response examples
  • Proper frontmatter with appropriate titles and descriptions
  • Correctly references the OpenAPI spec with openapi: get /v1/request/{requestId}/inputs

Practical use cases and context

  • Explains the connection to Prompt Management feature
  • Lists concrete use cases: regression testing, prompt comparison, debugging
  • Links to relevant documentation (/features/advanced-usage/prompts/overview)

Excellent response documentation

  • Shows both successful response with data and null response scenarios
  • JSON examples are well-formatted and realistic
  • Clearly explains when data would be null

Proper navigation integration

  • Correctly added to the Request section in API Reference at line 327
  • Maintains alphabetical ordering within the group
  • Follows existing navigation patterns

Important user guidance

  • Includes EU API warning snippet (consistent with other endpoints)
  • Notes 90-day retention period - critical for users planning testing workflows

Minor Observations

  • The version_id example uses truncation (1c7a86c8-...) which is fine for documentation
  • All internal links are properly formatted
  • Follows Helicone's documentation style and conventions

Technical Accuracy

The documentation correctly describes the endpoint's purpose and behavior:

  • Retrieves inputs for requests made through AI Gateway prompt management
  • Returns null when no inputs are associated (non-prompt-managed requests)
  • Proper JSON response structure matches typical Helicone API patterns

Suggestions Summary

No critical issues found. This is high-quality documentation that:

  • Provides clear value proposition for the endpoint
  • Includes practical examples developers can use immediately
  • Follows established documentation patterns
  • Properly integrates with existing navigation

The documentation is ready for merge and will help users effectively utilize this new endpoint for testing and debugging workflows.


Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant