# Intégration FTP avec l’API V4 – Besoin d’une passerelle technique pour upload automatique

**URL:** <https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504>\
**Category:** Help\
**Tags:** api, s2s\
**Created:** [May 23, 2025, 3:34pm UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504 "2025-05-23T15:34:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![soukoner](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@soukoner](https://forum.frame.io/u/soukoner)\
**Post date:** [May 23, 2025, 3:34pm UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/1 "2025-05-23T15:34:43Z")

</div>

Bonjour à tous,

Nous sommes en train de finaliser un pipeline de postproduction automatisé dans lequel nous transférons des fichiers vidéo depuis un serveur FTP (dédié à l’acquisition terrain) vers Frame  
Après avoir étudié en profondeur l’API V4, nous avons réussi à authentifier notre application, générer les tokens nécessaires, et comprendre le fonctionnement général de l’upload (création d’assets, PUT sur l’upload\_url, etc.).  
Mais voici notre problématique : **Frame ne propose pas de support FTP en natif** , ce que nous comprenons.

Nous avons donc tenté de créer un **bridge logiciel** (en Python), qui :

- télécharge les fichiers depuis notre FTP,

- puis les transfère automatiquement vers Frame via API.

- Cela fonctionne en théorie, mais en pratique :

- Nous rencontrons des erreurs 401 sporadiques malgré un token valide.

- Nous ne savons pas si ce type de workflow est “toléré” ou supporté techniquement par Frame.

- Il est difficile de trouver une documentation claire sur la façon d’utiliser des URLs pré-signées ou des endpoints spécifiques (comme ceux utilisés dans les workflows C2C type Atomos ou Teradek).

Notre question est donc simple :  
**Existe-t-il un moyen validé ou recommandé pour ingérer automatiquement des fichiers depuis un serveur distant (FTP ou autre) vers Frame via l’API ?**

Même une piste partielle (ex. : possibilité de générer des upload URLs à l’avance, best practices, webhooks à déclencher…) serait très utile pour éviter de maintenir une infrastructure maison qui pourrait ne pas tenir dans le temps.  
On est ouverts à discuter, en public ou en privé, avec un développeur de l’équipe, ou tout utilisateur ayant déjà tenté ce type d’intégration.

Dans l’attente de vos retours,

Remi

---

<div class="post-metadata">

**Author:** ![CharlieAnderson](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/charlieanderson/32/491_2.png) [@CharlieAnderson](https://forum.frame.io/u/CharlieAnderson)\
**Post date:** [May 30, 2025, 6:54pm UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/2 "2025-05-30T18:54:19Z")

</div>

@soukoner we do not specifically support FTP as a connection to [Frame.io](http://Frame.io), however our Server to Server authentication could be of value to you, however it is limited to Adobe Managed [Frame.io](http://Frame.io) Accounts at this time (currently scoped to Enterprise accounts, yet coming to all accounts in the future as I mentioned in our Early Access announcement post last month).

The `file.create` [endpoint](https://developer.adobe.com/frameio/api/current/#tag/Files/operation/files.create) should return the presigned urls to you when you make the call, provided you get a successful `201` response.

In practice, you would make the `POST https://api.frame.io/v4/accounts/{account_id}/folders/{folder_id}/files` call with your `file_size`, `media_type` and `name`, which will then then return the `upload_urls` within the `data` payload, such as this example that is on our documentation:

```auto
{
  "data": {
    "created_at": "2023-09-25T19:18:29.614189Z",
    "file_size": 1137444,
    "id": "2e82fa5d-cb60-4f57-a2ae-8887ca76203e",
    "media_type": "image/png",
    "name": "asset.png",
    "parent_id": "c2e43afb-4794-4268-adb9-34a95e73c811",
    "project_id": "d8145e89-d8cf-49a8-a3ed-087416b8460c",
    "status": "created",
    "type": "file",
    "updated_at": "2024-02-07T16:44:41.986478Z",
    "upload_urls": [
      {
        "size": 20000000,
        "url": "https://my.fileupload.url.dev"
      }
    ],
    "view_url": "https://next.frame.io/project/d5e6011c-2bc9-4596-be05-77d562627112/view/5a89a9fb-0900-4b23-826b-127b90e4db4c"
  }
}

```

Otherwise, you might be able to utilize our [remote-upload method](https://developer.adobe.com/frameio/api/alpha/#tag/Files/operation/files.create_remote_upload) which is in our Alpha version at this time.

You would use the following call:  
`POST https://api.frame.io/v4/accounts/{account_id}/folders/{folder_id}/files/remote_upload`

with a payload of

```auto
{
  "data": {
    "name": "asset.png",
    "source_url": "https://upload.wikimedia.org/wikipedia/commons/e/e1/White_Pixel_1x1.png"
  }
}

```

and also including `api-version:alpha` in the header request.

I personally have not tried this yet, and it’s still in alpha, but please give that a try and see if it will work for you from your FTP site!

---

<div class="post-metadata">

**Author:** ![rushiraj2407](https://avatars.discourse-cdn.com/v4/letter/r/b38774/32.png) [@rushiraj2407](https://forum.frame.io/u/rushiraj2407)\
**Post date:** [June 9, 2025, 10:24am UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/3 "2025-06-09T10:24:38Z")

</div>

Hi,  
I have a Python script that uploads a local file to Framiov4 using their API.  
Now, I’d like to understand how you handle server-to-server OAuth token generation.

---

<div class="post-metadata">

**Author:** ![soukoner](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@soukoner](https://forum.frame.io/u/soukoner)\
**Post date:** [June 11, 2025, 10:09am UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/5 "2025-06-11T10:09:05Z")

</div>

**Objet** : Petite précision sur remote\_upload et FTP OVH

Hi Charlie, hi Rushiraj,

First of all, thanks a lot for your previous answers — we are progressing very well.

We are finalizing a fully automated bridge between our acquisition server (FTP) and [Frame.io](http://Frame.io) API v4.

✅ Our current flow :

- The Sony FX3 camera dumps files on our FTP server (ftp…ovh.net - secured login, not publicly accessible)
- An AWS EC2 instance monitors the FTP, detects new files, and would normally:
  - Download locally → Upload to [Frame.io](http://Frame.io) → Delete after upload

- OAuth Web App flow is being finalized with Adobe Developer.

👉 Now, **our question** regarding your remote\_upload alpha feature:

- We perfectly understand that remote\_upload expects a source\_url in HTTPS.
- However, our FTP server is not publicly exposed in HTTPS.
- Do you support FTP(S) or authenticated HTTP sources for remote\_upload?
- Otherwise:
  - Would generating temporary pre-signed HTTPS links from our FTP storage solve the problem?
  - Or would you recommend that we stay with the standard “local download + API upload” approach?

Any confirmation would really help us make the final architecture decision.

Thanks again 🙏

Best regards,

Rémi

---

<div class="post-metadata">

**Author:** ![CharlieAnderson](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/charlieanderson/32/491_2.png) [@CharlieAnderson](https://forum.frame.io/u/CharlieAnderson)\
**Post date:** [June 11, 2025, 12:55pm UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/6 "2025-06-11T12:55:52Z")

</div>

Hi Remy,

We recently moved our [remote upload to stable](https://developer.adobe.com/frameio/api/current/#tag/Files/operation/files.create_remote_upload), so it’s no longer necessary to use the `alpha` header for it.

> - Do you support FTP(S) or authenticated HTTP sources for remote\_upload?

We do not at this time.

> - Would generating temporary pre-signed HTTPS links from our FTP storage solve the problem?

If this would generate a publicly exposed HTTPS url, then yes.

Either solution would work, but I would assume not doing a local download would save considerable time and resources. Would be very curious to see your workflow in action once you have it completed!

---

<div class="post-metadata">

**Author:** ![CharlieAnderson](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/charlieanderson/32/491_2.png) [@CharlieAnderson](https://forum.frame.io/u/CharlieAnderson)\
**Post date:** [June 11, 2025, 12:58pm UTC](https://forum.frame.io/t/integration-ftp-avec-l-api-v4-besoin-d-une-passerelle-technique-pour-upload-automatique/2504/7 "2025-06-11T12:58:02Z")

</div>

HI @rushiraj2407 [Server to Server](https://developer.adobe.com/frameio/guides/Authentication/#server-to-server-authentication) is only available to Adobe Managed accounts at this time (Enterprise). This is planned to come to all acounts in the future, as was stated in my original [announcement post](https://forum.frame.io/t/introducing-the-frame-io-v4-api-early-access-program/2407).