> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/faq-and-troubleshooting/file-picker-custom-api-storage.md).

# Custom API storage is missing from File Picker

In Classic App Builder, File Picker selects a storage configuration. If you have added a REST API resource but cannot select it for uploads, check whether a storage and its upload query have been configured.

## Check the storage setup

1. Open the resource's **Storages** section in the Data Editor.
2. Use **Create Storage** if the required storage has not been configured.
3. Configure the required **Upload** query for your storage.
4. Return to File Picker and choose **Save to Storage** as its output format.
5. Select the configured storage and test with a small, non-sensitive file.

See [Data Source Storage](https://docs.jetadmin.io/user-guide/data/file-storage-and-uploading/data-source-storage) for the setup flow and [File](https://docs.jetadmin.io/classic-app-builder/design-and-structure/components/fields/file) for File Picker settings.

## I cannot bind the upload parameters

Check the upload endpoint's required body fields and encoding. The upload-query editor may not expose the same controls as the general REST API builder.

If a required input or binding control is unavailable, send support the app URL, storage type, required parameter names, and a sanitized screenshot of the upload-query editor. Explain which file or metadata value you need to pass. Do not include API keys or authorization headers.

## Verify the upload

Check that the file reaches the intended storage and that the app record references the intended file. Confirm access using an end-user account before making the upload flow available to customers.

*Last reviewed: September 16, 2026.*


---

# 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.jetadmin.io/faq-and-troubleshooting/file-picker-custom-api-storage.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.