> For the complete documentation index, see [llms.txt](https://docs.linkdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linkdrop.io/linkdrop-dashboard/creating-links-in-bulk/individual-qr-codes/connecting-qrs-to-claim-links.md).

# Connecting QRs to claim links

The QRs that you create, are **by default not connected** to any claim links. \
\
So, such QRs should be considered as a container for future claim links, while the links were not yet added. Such QRs will lead to the page stating "QRs not mapped". \
\
**Connecting QRs** (or the proxy links that they're generated from) allows you to switch them to point to the actual claim links. Once your QRs are connected, by scanning them - you will have the claim application opened and can start the claiming process.

{% hint style="info" %}
Such flow enables you to generate a batch of QRs quickly to start arranging their physical printing and distribution. Meanwhile, you can work on the NFT collection, and when you're ready - create claim links and connect them
{% endhint %}

#### To connect QRs to claim links you will need to:

* *Prerequisites:* create the Campaign, and download the CSV file with links. The quantity of links in the CSV file should be equal to the number of QRs you want to connect them to 
* Press the "Upload file" button in the "Connect to claim links" section. Select the file and press "Upload" on the pop-up screen. If you have uploaded the file in the incorrect format, you will see an alert "Invalid file. File should be downloaded from campaigns page"

{% hint style="info" %}
Once the QRs are connected, you will no longer be able to change the QR quantity in a set. Users who have those QRs can start claiming tokens. 
{% endhint %}

\
\ <br>


---

# 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.linkdrop.io/linkdrop-dashboard/creating-links-in-bulk/individual-qr-codes/connecting-qrs-to-claim-links.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.