> 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/hardware/wristband-printers.md).

# Wristband printers

Just click and print, simple as that

One of the services Eventication can deliver is wristband printer. Find out more detailled information about these devices [here](https://docs.eventication.com/event/misc/wristbands.md).

### Overview <a href="#list" id="list"></a>

This page displays a list of the rented devices with their current status.

### Usage <a href="#usage" id="usage"></a>

Here you can find an overview of the usage of the device. For wristband printers you will see a table that has the different devices in the rows and the different event days in the columns. Per day per device you get a number of wristbands printed. Next to each device name, a badge shows whether the device is currently online or offline. At the bottom and at the right side of the page you can find cumulative information about a single device or a single day. In the right botton corner you can find the total number of wristbands.

{% hint style="info" %}
Please note that the usage numbers are calculated once per hour.
{% endhint %}

To place your order, please go to the [Hardware](https://docs.eventication.com/event/hardware/scan-app-devices.md) section in your event and click on [orders](https://docs.eventication.com/event/hardware/orders.md).


---

# 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/hardware/wristband-printers.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.
