422 Invalid fields in form error when uploading a PDF using your API from a Deno/Supabase Edge environment

I am encountering a persistent 422 Invalid fields in form error when uploading a PDF using your API from a Deno/Supabase Edge environment, while the exact same file and payload works perfectly with Postman.

I have compared both requests using webhook.site, and both Deno and Postman produce identical uploads:

• Same file field with the same name, size, and type

• Same model_id field

• Same Content-Type header, boundaries, and request headers

Can you advise if there are any subtle differences in multipart encoding, CRLF usage, or runtime detection that could cause your server to reject a Deno-generated multipart form, even when it is indistinguishable from Postman's upload?