> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aigenda.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Upload methods

> File, URL, YouTube, or a meeting bot: which one to choose.

Every method creates a recording in a space. Processing and the result are the same after that.

| Method | When it fits | Request |
| - | - | - |
| [File](/en/upload/file) | The file is on your disk or in your service's memory | `POST /api/spaces/{space_id}/audio/` and an upload to storage |
| [By URL](/en/upload/url) | The file is available at a direct link: cloud storage, telephony, CRM | `POST /api/spaces/{space_id}/audio/by_url/` |
| [YouTube](/en/upload/youtube) | The video is published on YouTube | `POST /api/spaces/{space_id}/audio/by_youtube/` |
| [Meeting bot](/en/upload/meeting-bot) | A Zoom, Google Meet, or Yandex Telemost meeting is in progress or starts soon | `POST /api/space/{space_id}/meeting/` |

## After the upload

A bot recording is processed on its own, so you only poll for its result. For a file, a URL, and YouTube the steps are the same:

1. Wait for `is_uploaded: true` in [`GET …/audio/{audio_id}/info/`](/en/api-reference/audio/info). For a file this takes less than a second. AiGenda downloads URLs and YouTube videos itself, which takes from a few seconds to several minutes.
2. Start [processing](/en/processing/start).
3. Poll the [result](/en/processing/status).

<Warning>
  Do not start processing before `is_uploaded: true`. AiGenda has not received the whole file yet, and processing will fail.
</Warning>

Format and title limits are the same for all methods: [Formats and limits](/en/upload/formats).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.