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

# File uploads

The Ultimo REST API is able to receive file uploads. There are two ways to send files:

* Sending multipart/form-data content
* Using Base64 encoded strings in the request body

For both options, it is required to create a specific workflow in Ultimo by a consultant to process these requests correctly. 

It is recommended to send files using multipart/form-data format. Using Base64 encoding increases the file size by approximately 33%, resulting in larger payloads and additional processing time. Additionally, multipart/form-data supports transmitting larger files (see Limits and Quotas).

*Example of a multipart/form-data request*

```
curl --location "https://customer.ultimo.net/api/v1/action/_REST_UploadFile" ^
--header "applicationelementid: 99999999-9999-9999-9999-999999999999" ^
--header "apikey: 99999999999999999999999999999999" ^
--form "File=@C:/temp/Manual.pdf" ^
--form "JobId=123456789"
```

An example of how to use base64 in requests can be found [here](/api-key-templates/jobs/attach-or-change-images.md).


---

# 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.ultimo.net/api-guide/rest/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.