> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/client-libraries/redivis-python/reference/parameter.md).
# Parameter
## *class* Parameter
An interface for working with workflow parameters on Redivis. Parameters are used to store sets of values that can be referenced across transforms and notebooks in a workflow.
## Constructors
## Examples
import redivis
workflow = redivis.workflow("username.workflow_name")
parameter = workflow.parameter("my_param").create(values=["foo","bar"])
print(parameter.get_values()) # ["foo", "bar"]
parameter.update(values=["hello","world"])
print(parameter.get_values()) # ["hello", "world"]
## Attributes
| Name | Description |
|---|
workflow | A reference to the Workflow instance that is associated with this parameter. |
properties | A dict containing the API resource representation of the parameter. This will only be populated after certain methods are called, particularly the get method, and will otherwise be None. |
qualified_reference | The fully qualified reference to this parameter For example, imathews.example_workflow_climate_analysis:x7kh.my_param:27sa
|
scoped_reference | The canonical reference for the parameter, without any qualifiers. E.g., my_param:27sa |
## Methods
| Method | Description |
|---|
parameter.create(*, values, type) | Create a new parameter within a workflow |
parameter.delete(*, values, type) | Delete a parameter |
parameter.get() | Fetches the parameter, after which parameter.properties will contain a dict with entries corresponding to the properties on the parameter resource definition. Will raise an error if the parameter does not exist. |
parameter.get_values() | Fetches the list of values associated with the parameter. |
parameter.exists() | Check whether the parameter exists. |
parameter.update([*, name, values, type]) | Update the parameter's name, values, and/or type. |
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.redivis.com/api/client-libraries/redivis-python/reference/parameter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.