# Activity List (Mapping)

The ***ActivityListRequest*** allows you to pull a list of available activities and options from the specified supplier. The activity list will include descriptive fields, options and the specific activity value to be used on subsequent API calls where a single activity is requested by your implementation.

It is the responsibility of any integration to store the unique activity codes for further API calls, where it is required.

{% hint style="info" %}
**Note:** Your implementation must store the returned activity codes for future calls, where required. The ActivityListRequest should be called periodically, since the supplier can update the available activities on the Zaui IO channels anytime, potentially making your stored activity codes stale.

**Note:**  Depending on the number of allowed activities that the supplier you are communicating with has provided for you, the data size on this call back can be large. As a result, it’s not uncommon to see this callback having a large data set. This call can often take up to 30 seconds to complete.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.zaui.com/io/api-function-definitions/activity-list-mapping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.