Skip to main content

​
Short answer

When the image URL passed to the API ends with a cloud-storage processing parameter such as ?x-oss-process=..., the API returns the “image content does not match MIME type” error. To fix it, strip the processing parameter from the URL and pass the raw direct link to the API, or download and reprocess the image on your own server before uploading it.

​
What does the error look like?

The error response is:
A typical triggering URL looks like:
The ?x-oss-process=... suffix is the image-processing parameter used by Alibaba Cloud OSS and similar object-storage services. Image generation endpoints on APIYI are known to return the error above when URLs contain this kind of parameter.

​
Known affected parameter names

The following parameter name has been reported to trigger this error when present on an image URL:
  • x-oss-process
If you use image-processing parameters from other cloud-storage providers (such as the equivalent parameters on Tencent Cloud COS or Huawei Cloud OBS), follow the same steps below before passing the URL to the API.

​
Steps to fix it

1

Strip the processing parameter from the URL

Copy the raw direct link of the image (without any ?x-oss-process=-style parameter) and pass it to the API again.For example, change:
to:
2

If you need size adjustment, process the image on your server first

If your workflow actually depends on OSS-side compression or cropping, first download the processed image from your bucket to local storage, then upload it via local path or a new parameter-free direct link.

​
Notes

Keep image URLs passed to the API as plain direct links with no trailing parameters, otherwise this error may be triggered.

​
If it still does not work

  • Confirm the URL can be opened directly in a browser, and that the real image format shown by the browser (right-click → inspect) matches the URL extension (jpg / png / webp)
  • If you are using an image-processing parameter from a different cloud-storage provider, contact technical support with the full error JSON and the request ID