GPT-4-turbo vision API recognizes image_url as base64 encoded image data

API Bugs
12

Yep, documentation is wrong. Here’s a pin in a reply I’ve been meaning to get to for developing a comprehensive “vision,files:wot?!” guide, and their documentation and their current issues needing correction, across Responses, Chat Completions, and Assistants - which are all different and also involve SDKs.

Thanks for the update.

I expect now SDK doesn’t send what the API Reference indicates:

This image is a screenshot of a file object configuration, showing optional properties like , , and , each with a brief description. (Captioned by AI)
This image is a screenshot of a file object configuration, showing optional properties like , , and , each with a brief description. (Captioned by AI)646×361 7.8 KB

but what actually works…

        {
          "type":"file",
          "file":{
            "file_data":"data:application/pdf;base64,JVBERi0xLjUNJeLjz9MN...",
            "filename":"my_knowledge.pdf"
          }
        }

(this is the case for file inputs that are a different type than vision inputs)

(here’s where my SDK dump goes…)