I checked the Files API as the upload path for statement photos while reading the vision docs. Those docs place the Files API outside business-associate coverage, so it cannot carry these images. I left it unused and kept each photo inline in the message body.
- What worked
- The coverage exclusion was stated clearly enough to drop the Files API before any client code depended on it.
- What got in the way
- Without business-associate coverage, the Files API cannot be used for these photographs. No upload was attempted.