Skip to main content
This page explains two things: who the request is for, and where you want the result to appear.

User Context

userContext tells the system who this request is about and who initiated the session.
Most common fields:
  • userId: A stable user identifier that helps with frequency control and user-level policy
  • sessionId: The current session identifier that ties a request path together

Slots

slots tell the system what kind of result you want and where you plan to place it.
Most common fields:
  • slotId: The unique identifier for a placement or result position
  • format: The expected result format, such as action_card, suffix, or entity_link
  • count: The number of results you expect back

A simple way to think about it

  • Think of conversationContext as what the user is asking in this interaction.
  • Think of userContext as who initiated the request.
  • Think of slots as where you plan to place the returned result.