> For the complete documentation index, see [llms.txt](https://doc.bunq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.bunq.com/api-reference/attachment.md). # Attachment **Attachments** in the bunq app allow users to attach images or text to payments, making it easy to reference receipts, invoices, or any relevant information later. Each attachment is linked to a Monetary account. Each attachment must have a specific file type, such as JPEG, PNG, or PDF, and the file is first uploaded to a monetary account before it can be linked to any payment. The process involves multiple steps: 1. **Create the attachment -That is this page-.**\ Users must first upload the file to the monetary account. This step requires providing the file itself along with a brief description. Bunq stores the attachment securely and returns a unique attachment ID, which will be used in the next step. 2. **Link the attachment to a payment:** Once the attachment exists, it can be linked to a specific payment as a **note-attachment**. This allows users to associate files like receipts or invoices directly with a transaction for easy retrieval. An optional description can also be added to give context to the attachment within the payment. To see how to do this reference [Payment](/note-text-and-attachment/payment.md) 3. **Add text notes (optional):** Separately, users can also add plain text notes to a payment as a **note-text**, without uploading a file. This is useful for quick comments, explanations, or any textual reference that supplements the payment. [Note Text & Attachment](/note-text-and-attachment.md) {% openapi src="" path="/user/{userID}/monetary-account/{monetary-accountID}/attachment" method="post" %} {% endopenapi %} {% openapi src="" path="/user/{userID}/attachment/{itemId}" method="get" %} {% endopenapi %} --- # 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://doc.bunq.com/api-reference/attachment.md?ask=&goal= ``` `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.