> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/integrations/ticketgrid/products.md).

# Products

This is a list of products that are synced from Ticketgrid to Eventication. We're given some information like

* Name of the product
* Amount available

These datapoints can help you identify the correct product for when you start distributing the tickets between [members](/event/planning/members/ticket-integration.md) and [list forms](/event/accreditation/lists/forms/ticket-integration.md).

Open up a product and you can click the *Use on eventication?* badge to toggle using this product on our platform or not.

## Sync

The platform will sync the product data and new products to the platform **every hour**. You can manually trigger a sync by clicking the <img src="/files/Xj3wR1H5kJC3Gh2cEUYj" alt="" data-size="line"> button. This sync happens in the background so give it some time and refresh your page.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eventication.com/event/general/integrations/ticketgrid/products.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.