Issue with Data Schema Generation for Upload Collections

[fabioquarantini]

Currently, when a collection supports uploads, the data schema generated for the POST request is incorrect.

[janbuchar]

Hi, thanks for the report, can you please share the current gnerated spec and the desired result?

[fabioquarantini]

Hi! I’m attaching a draft of what I have in mind. Let me know what you think.

[janbuchar]

Can you please explain what to look for in those screenshots? Or, if you could give me an example payload config and show me what is incorrect in the generated OpenAPI JSON, it would be much easier to fix this.

[fabioquarantini]

The issue is with the POST generated schema: when a collection has upload: true, Payload does not accept all fields directly in the request body. It expects a multipart/form-data request with:

• file: the binary file
• data: optional, a JSON string containing additional fields (title, alt, etc.)

The current schema includes these fields as top-level properties (title, url, etc.), but this is not compatible with the Payload API.
The second image I shared shows a similar format to what Payload actually expects.

📄 Official documentation reference:
https://payloadcms.com/docs/upload/overview#uploading-files