File upload to Xano: needs multipart/form-data and user authentication.
@Erik Beuschau
We 're currently working on improving our entire API setup , making it easier to work with API requests in general . We 're still debating internally whether our API proxy should support file uploads at all though - here are our thoughts so far : - Opening up for proxying file uploads would add a potential significant cost on our side since users could upload large (10 +GB ) files - We don 't think it is a best practice to upload files anywhere else than the final destination where the endpoint is usually optimized for receiving large files Generally , toddle tries to be a front -end tool only - however , we 've added support for proxying requests to make it easier /possible to work with authenticated APIs /back -ends such as Supabase , Xano and Buildship by forwarding a cookie to avoid cross origin issues . So you could look at the file upload restriction in 2 ways I suppose : - It 's a limitation /error on toddle 's side that the proxy doesn 't support this - It 's a service that file upload services should provide the necessary tools (signed /temporary upload urls ) for , and not the responsibility of toddle to fix As mentioned in some of the other threads , both Supabase and Amazon S3 do have support for unique file upload urls , but it seems you would need to build that functionality manually on Xano /Buildship unfortunately . I hope the above makes sense . Let us know if you find a solution that could potentially be shared with the rest of the community 🙏 The only ressources I could find on the topic were these : - https://docs.xano.com/working-with-data/cloud-storage#signed-url - https://legacy-community.xano.com/discussion/4180106/upload-file-to-s3-signed-url - https://community.xano.com/ask-the-community/post/how-to-create-google-cloud-storage-signed-urls-for-each-item-in-a-mPeVJY2XX8mcNQw
.jpeg/public)