> For the complete documentation index, see [llms.txt](https://docs.hello-lisa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hello-lisa.com/developers/guides/integration-guide/entrypoints/query-parameter-v1.md). # Query Parameter (v1) {% hint style="info" %} The parameters outlined on this page are applicable exclusively to LiSA Player version 1. {% endhint %}

Name Description

Name	Description
`replay_time`	The `replay_time` parameter specifies the starting point for a show recording. By providing a numeric value, you can determine the exact time, in seconds, at which the playback should begin. Accepted Value: Any non-negative numeric value representing the desired start time in seconds. (e.g., `0` for the beginning of the recording, `60` for one minute into the recording, etc.)
`ui_close_icon`	The `ui_close_icon` parameter specifies space reservation in the player's header for an external UI control, such as a close button. This ensures that external UI elements do not overlap with the player's built-in controls. Value Pattern: `(left\|right)(:width)?(:height)?` `left` or `right`: Specifies the side of the viewport where the space is reserved. `:width` (optional): The width of the reserved space, specified as a valid CSS length (e.g., `32px`, `2em`). If omitted, the default width is `32px`. `:height` (optional): The height of the reserved space, specified as a valid CSS length. If omitted, the default height matches the width. Default Behavior: If only the side (`left` or `right`) is provided, a default space of `32x32px` is reserved. If one additional value is provided, it applies to both width and height. If both width and height are provided, they are applied independently. Example Usage: Default size on the right — Reserves `32x32px` in the top-right corner `ui_close_icon=right` Custom size on the right — Reserves `42x42px` in the top-right corner `ui_close_icon=right:42px` Custom width and height on the left — Reserves `50px` width and `40px` height in the top-left corner. `ui_close_icon=left:50px:40px`
`url_params`	The `url_params` parameter allows you to append custom query parameters to URLs exposed by the LiSA Player, such as those used for social sharing or add-to-calendar options. This enables you to include additional data or tracking parameters in a structured and URL-safe manner. Usage Guidelines: Provide the query parameters in URL-encoded form. Use standard query string syntax: `key1=value1&key2=value2`. Example Usage: To append `utm_source` and `utm_campaign` parameters: `url_params=utm_source%3Dsocial%26utm_campaign%3Devent_launch` To append a custom parameter: `url_params=ref_id%3D12345` This parameter allows you to extend the functionality of URLs for tracking or customization, ensuring seamless integration with your workflows and analytics tools.

replay_time

The replay_time parameter specifies the starting point for a show recording. By providing a numeric value, you can determine the exact time, in seconds, at which the playback should begin.

Accepted Value:

Any non-negative numeric value representing the desired start time in seconds.
(e.g., 0 for the beginning of the recording, 60 for one minute into the recording, etc.)

ui_close_icon

The ui_close_icon parameter specifies space reservation in the player's header for an external UI control, such as a close button. This ensures that external UI elements do not overlap with the player's built-in controls.

Value Pattern: (left|right)(:width)?(:height)?

left or right: Specifies the side of the viewport where the space is reserved.
:width (optional): The width of the reserved space, specified as a valid CSS length (e.g., 32px, 2em). If omitted, the default width is 32px.
:height (optional): The height of the reserved space, specified as a valid CSS length. If omitted, the default height matches the width.

Default Behavior:

If only the side (left or right) is provided, a default space of 32x32px is reserved.
If one additional value is provided, it applies to both width and height.
If both width and height are provided, they are applied independently.

Example Usage:

Default size on the right — Reserves 32x32px in the top-right corner

ui_close_icon=right

Custom size on the right — Reserves 42x42px in the top-right corner

ui_close_icon=right:42px

Custom width and height on the left — Reserves 50px width and 40px height in the top-left corner.

ui_close_icon=left:50px:40px

url_params

The url_params parameter allows you to append custom query parameters to URLs exposed by the LiSA Player, such as those used for social sharing or add-to-calendar options. This enables you to include additional data or tracking parameters in a structured and URL-safe manner.

Usage Guidelines:

Provide the query parameters in URL-encoded form.
Use standard query string syntax: key1=value1&key2=value2.

Example Usage:

To append utm_source and utm_campaign parameters:

url_params=utm_source%3Dsocial%26utm_campaign%3Devent_launch

To append a custom parameter:

url_params=ref_id%3D12345

This parameter allows you to extend the functionality of URLs for tracking or customization, ensuring seamless integration with your workflows and analytics tools.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hello-lisa.com/developers/guides/integration-guide/entrypoints/query-parameter-v1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.