continuation_token
A self-contained encrypted payload returned in the Gemini API continuation protocol. It encodes the original prompt hash and the generation position, enabling the server to resume generation without maintaining session state.
Timeline (last 90 days)
The continuation_token is a self-contained encrypted payload that internally encodes the original prompt hash and the generated position pos, rather than a server-side session ID.
When using the continuation_token to resume generation, the prompt must be byte-for-byte identical, otherwise the hash check fails and returns HTTP 400.
Under the continuation protocol, requests must remain completely identical, and each resend must include the content, system instructions and tools, because the token carries the hash of the original prompt.
All Facts (3)
The continuation_token is a self-contained encrypted payload that internally encodes the original prompt hash and the generated position pos, rather than a server-side session ID.
50%UnverifiedWhen using the continuation_token to resume generation, the prompt must be byte-for-byte identical, otherwise the hash check fails and returns HTTP 400.
50%UnverifiedUnder the continuation protocol, requests must remain completely identical, and each resend must include the content, system instructions and tools, because the token carries the hash of the original prompt.
50%