> For the complete documentation index, see [llms.txt](https://developers.airship.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.airship.co.uk/basics/vouchers.md).

# Vouchers

Airship has the ability to store and generate unique vouchers, associate them to a contact and act as a gatekeeper for if a voucher is active, or has been redeemed.

Airships APIs allows partners (typically POS) to;

* Create unique code groups
* Check the status of a voucher code
* Redeem a voucher code

Vouchers are contained in Unique Code Groups - Which is a collection of vouchers for a single purpose - I.e. a specific offer might be for a 'Free cup of coffee' - in which case a Unique Code Group will be created for that offer and all the relevant vouchers generated within that group.

When a partner attempts to check the status, or redeem a voucher code - The clients Account ID and Unique Code Group ID must be provided to Airship so the correct voucher is validated&#x20;


---

# 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://developers.airship.co.uk/basics/vouchers.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.
