> 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/tickoweb.md).

# Tickoweb

Ticketing using our platform

This guide will help you integrate <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2FySQZ985OarFNCu675iRT%2Ftickoweb.svg?alt=media&amp;token=d3744d6a-e78f-4360-857f-6742bde165bf" alt="" data-size="line"> [Tickoweb](https://www.tickoweb.be) with your Eventication platform. This powerful integration allows event organizers like you to extend the capabilities of Eventication by leveraging Tickoweb for entry ticket management. Let's dive into the details of how this integration works and how you can make the most out of it.

## Overview

By connecting Tickoweb with your Eventication account, you now have the ability to issue actual entry tickets directly to your [members](/event/planning/members.md) or [list visitors](/event/accreditation/lists/forms.md). This feature will save you a lot of time and clicks.

## Key Features <a href="#key-features" id="key-features"></a>

* **Direct ticket issuance**: Send actual entry tickets to your members and list visitors superfast.
* **Enhanced attendee experience**: Issuing actual tickets contributes to a more positive and engaging experience for receivers while never leaving the Eventication website.
* **Unlimited tickets**: There is no cap on the number of tickets you can issue through this integration. It has been designed to accommodate events of all sizes. The only limit is the one you set on a ticket. Sold out = sold out!
* **Cost-free integration**: This integration is offered at no additional charge for all current and future Eventication customers, aligning with our commitment to providing value-added services.
* **Automated ticketing for members**: Connect tickets to our rewarding system, enabling automated distribution based on various filters.
* **Moderator permissions**: Control who can issue tickets within your organization by utilizing moderator permissions.

{% hint style="info" %}
We only allow **one** ticket partner to be integrated per event.
{% endhint %}

## Getting Started <a href="#getting-started" id="getting-started"></a>

{% stepper %}
{% step %}

### Add the integration

On your event's [integrations](/event/general/integrations.md) page, select 'New' and add the Tickoweb integration. If you don't see Tickoweb, contact your account manager.
{% endstep %}

{% step %}

### Get your API key

To validate the integration, install the Eventication integration in Tickoweb and create an `Eventication` channel to access your `API key`. Once you have done this, copy the API key value, paste it in the API key field on Eventication and click `Save`. If the key is accepted by Tickoweb, you will see a <mark style="color:green;">green</mark> confirmation box popping up.
{% endstep %}

{% step %}

### Validated!

Eventication has validated the integration and will automatically retrieve all the products (ticket types) in your Tickoweb account.
{% endstep %}

{% step %}

### Done!

That's it! The Tickoweb integration is now live 🎉. From now on you can add tickets for your [list forms](/event/accreditation/lists/forms/ticket-integration.md) or your [members](/event/planning/members/ticket-integration.md).
{% endstep %}
{% endstepper %}


---

# 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/tickoweb.md?ask=<question>&goal=<user_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.