> For the complete documentation index, see [llms.txt](https://docs.startrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.startrail.io/issue-transfer-api.md).

# Issue transfer api

- [Issue & Transfer SRR (NFT)](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft.md)
- [Issuance Flow (End-to-End)](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/issuance-flow.md): End-to-end recommended flow for issuing SRRs — single and bulk, with new files or reusing previously uploaded files. Flowcharts + step tables.
- [Request Signed URL for Upload/Download Files](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/request-signed-url-for-upload-download-files.md): to generate signed URLs both for uploads and downloads
- [File Information Metadata](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/file-information-metadata.md): to get file metadata
- [Issue & Transfer](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/issue-and-transfer.md): to issue or issue+transfer SRR
- [Request Payloads & Recipes](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/payloads.md): Copy-paste request payloads for every Issue & Transfer scenario — issue to self, issue-on-buyer, custom collection, NFC tags, attachments and bulk.
- [Errors & Troubleshooting](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/errors.md): Every error the Issue & Transfer SRR API family can return — HTTP status, exact message, cause, and how to fix it.
- [Webhook Setup](https://docs.startrail.io/issue-transfer-api/issue-and-transfer-srr-nft/webhook-setup.md)
- [Collection](https://docs.startrail.io/issue-transfer-api/collection.md)
- [Create Collection](https://docs.startrail.io/issue-transfer-api/collection/create-collection.md): to create a new collection
- [Get Collection of LUW](https://docs.startrail.io/issue-transfer-api/collection/get-collection-of-luw.md)
- [Change Logs](https://docs.startrail.io/issue-transfer-api/change-logs.md): Summary of the changes, updates, and fixes made to the Issue & Transfer API
- [v1.3.0](https://docs.startrail.io/issue-transfer-api/change-logs/v1.3.0.md): @May 12, 2026
- [v1.2.0](https://docs.startrail.io/issue-transfer-api/change-logs/v1.2.0.md): @April 26, 2023
- [v1.1.0](https://docs.startrail.io/issue-transfer-api/change-logs/v1.1.0.md): @Oct 18, 2022
- [v1.0.1](https://docs.startrail.io/issue-transfer-api/change-logs/v1.0.1.md): @Aug 30, 2022


---

# 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.startrail.io/issue-transfer-api.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.