Skip to main content
For example, you can use embed URL parameters to:
  • Specify user content roles
  • Assign connection and model roles to users
  • Control the look and theme of your embedded application
  • Apply user attributes to users
How these parameters are included in an embed URL depends on its signing format. In the v1 signed payload format, all parameters are carried inside a single payload parameter, and JSON-valued parameters such as userAttributes stay as JSON instead of being stringified and URL encoded. In the legacy v0 format, each parameter is sent as its own URL parameter.A v1 payload also carries an exp expiry that isn’t listed below as it isn’t something you set per session in the same way. See URL expiry for more information.

Required parameters

At a minimum, valid embed requests must contain all of the following parameters: The following parameters are strongly recommended, but not required, in embed requests.

Optional parameters

The following parameters are optional in embed requests.