> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/rewards-redemption/rewards/reward-categories.md).
# Reward Categories
In this section, you will get to know how to set up Reward categories and how to use them in the Open Loyalty panel.
## The reward categories list
## Adding a reward category
To add a category, click the **Add category** button in the upper right corner. A dialog opens:
Data that needs to be filled in to set the category correctly:
* **Category name** (required)
* **Active** - switch it on to activate the reward category
Optionally, click **+ Translations** to add the category name in the other languages set up in Translations.
Click **Add category** to save it.
When you set a reward category, you can use it as a filter in the **All rewards** list: click **Add filter**, choose **Categories** from the attribute list, and select the categories:
***
## Managing reward categories
#### Searching via the Table Search
\
To find the specific reward category, you use a Search Table available in the upper right corner under the 'Add Category' button. The search field allows you to find the reward category via the name:
Once you start typing the reward category name, the results will change automatically.
---
# 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://help.openloyalty.io/rewards-redemption/rewards/reward-categories.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.
