docs: update Responses API page for Gemini stateful conversations - #1072
Open
naresh4dev wants to merge 6 commits into
Open
naresh4dev wants to merge 6 commits into
naresh4dev wants to merge 6 commits into
Conversation
…tags Add a comprehensive guide covering end-to-end setup for forwarding Portkey metadata as AWS STS session tags during Bedrock AssumeRole calls. Covers gateway configuration, IAM permissions (caller + target trust policy), SDK/cURL examples, CloudTrail verification, Cost Explorer activation, tag sanitisation constraints, credential caching, and troubleshooting common errors. Also updates the existing assumed-role doc with minimum gateway version, clearer IAM guidance, and a cross-link to the new cookbook.
- Replace real AWS account IDs and role names in the troubleshooting error example with generic placeholders - Expand the Credential Caching section with: cache key composition table, TTL details, cache backend (Redis vs in-memory), when new AssumeRole calls happen, STS call volume estimation formula, and a note about throttling for high-cardinality metadata
Remove the raw cache key format string (internal implementation detail) while keeping the parameter table and 'not in cache key' clarification that are useful for users.
Replace the box-drawing character diagram with a Mermaid sequenceDiagram that Mintlify renders natively with interactive zoom/pan controls.
- Move IAM permission setup (caller policy + trust policy) to Step 1 - Move gateway env flag enablement to Step 2 with a warning to complete IAM setup first to avoid AccessDenied on all requests - Add enterprise self-hosted note at the top - Update all step references in troubleshooting section
- Move Google Gemini and Vertex AI from adapter to native providers list - Add 'Stateful Conversations (previous_response_id)' section with Python, JavaScript, and cURL examples for Gemini - Update Native-Only Features section to document Google support for previous_response_id, store, and retrieve/delete operations - Note that Portkey maps previous_response_id to Gemini's native previous_interaction_id via the Interactions API
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update the Responses API docs to reflect Google Gemini and Vertex AI as native providers with
previous_response_idsupport.Related: gateway-enterprise-node PR #2063
Changes
previous_response_id,store, and retrieve/delete operationsprevious_response_idto Gemini's nativeprevious_interaction_idvia the Interactions API