> 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/event-square/products.md).
# Products
The See Tickets products
This is a list of products that are synced from EventSquare 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 
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.eventication.com/event/general/integrations/event-square/products.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.