# Using AXS with multiple types

First of all u need the direct even link, I.E:\
<https://www.axs.com/events/490631/kcon-la-2023-day-1-tickets>\
You'll notice that if we press "GET TICKETS", we aren't redirected to the ticket page, instead to the splash page to the event.\
\
To add that event we will go to the redirect page, then grab the type of tickets we want by right clicking the type we want, and click copy url:\
For example\
![](/files/8rbB0F9h5JVaOIBiH8Pc)

\
\
Will give us this link:\
<https://shop.axs.com/?c=axs&e=59018463754070786&t_skin=kcon>\
OR\
<https://bit.ly/3OHvvgC><br>

### For shop.axs links

\
Then we can just copy the event id from the url, and tack it on at the end of our normal url\
`https://www.axs.com/events/490631/kcon-la-2023-day-1-tickets?event=59018463754070786`

We can just add that link to our monitor using the $monitor command.

### For bit.ly links

\
Then we can just copy the bitly id from the url, and tack it on at the end of our normal url\
`https://www.axs.com/events/490631/kcon-la-2023-day-1-tickets?bitly=`3OHvvgC

We can just add that link to our monitor using the $monitor command.


---

# 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.moonitor.tools/monitoring-commands/using-axs-with-multiple-types.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.
