In-app parameters vs dynamic embedded parameters

Use an in-app parameter for a value saved with the request. Examples include Content-Type: application/json, a stable provider setting, or a sensitive request credential that must stay server-side.

Use a dynamic embedded parameter for a runtime value that can change on each call. For example, storefront code can pass the ID of the product currently being viewed instead of saving one product ID on the request. Dynamic embedded parameters are also called runtime parameters or embedded parameters.

Both forms use the same locations: headers, query parameters, path parameters, body, Flow parameters, Liquid parameters, and supported System parameters. If a saved parameter and dynamic embedded parameter have the same name in the same location, the dynamic embedded value overrides the saved value for that execution.

Start with the request parameters overview, then use the in-app parameter or dynamic embedded parameter pages for setup details.