> For the complete documentation index, see [llms.txt](https://developer.textmaster.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.textmaster.com/overview/file-uploads.md).

# File uploads

Learn how to upload files using the TextMaster REST API

You are free to use your own storage service and provide us with the publicly accessible URLs which will be used to copy your files when creating documents.

If you don't use a storage service or would prefer to upload your files on TextMaster, you can use our [Uploads](/reference/uploads.md) endpoint which consist of the following steps:

1. Retrieving the file upload properties from the API.
2. Make a request using the file upload properties and passing signed metadata as HTTP headers.

{% hint style="info" %}
**Tips:** TextMaster uses a temporary storage to store your files until they are linked to a document. They will be automatically deleted after a period of 60 days from this temporary storage location.
{% endhint %}

For more information about how to use this endpoint, see:

{% content-ref url="/pages/KvEl5i49nrCsyBsXp4ZU" %}
[Uploads](/reference/uploads.md)
{% endcontent-ref %}


---

# 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://developer.textmaster.com/overview/file-uploads.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.