Skip to main content
When starting tasks through the API, you’ll often need to provide assets like images. Some exist for what you can provide.

​
URLs

In all cases, URLs must meet some basic minimum requirements:
  1. All URLs must be HTTPS.
  2. URLs must reference a domain name, not an IP address.
  3. The server should respond with valid Content-Type and Content-Length headers.
  4. Redirects are not followed. If the URL returns a 3XX response code, the request is considered failed.
  5. The length of any single URL should not exceed 2048 characters.
Additionally, the server responding to the request must support HTTP HEAD requests.

​
Content-Type

When specifying a URL, the Content-Type response header must be specified, and it must match the media type of your asset. File extensions in URLs are not considered. The Content-Types that are supported are listed below for the supported asset types.

​
User Agent

Infinite Creator will use a User-Agent header that starts with InfiniteCreator/ when making requests to your server. If you use a scraping-prevention tool or WAF, be sure to allowlist our user agent string prefix.

​
Type-specific requirements

​
Images

For fields that accept images, the asset referenced by the URL must use one of the following codecs, along with the corresponding Content-Type header:
CodecContent-Type
JPEGimage/jpg or image/jpeg
PNGimage/png
WebPimage/webp
And fit the following constraints:
PropertyLimit
ResolutionUp to
Size —
  • It is not recommended to provide images smaller than 640x640px or larger than 4K.
  • If your image has an EXIF Orientation flag set, we will rotate it to the correct orientation.
  • Although we don’t impose an aspect ratio limit, we crop every image to ensure that its aspect ratio falls within the range between 0.5 and 2.0 as necessary. Cropping is done from the center of the image.