https://ik.imagekit.io/your_imagekit_id. The first origin that you add automatically becomes accessible through this default URL endpoint.
https://ik.imagekit.io/your_imagekit_id/product-images/, then enter product-images in this field.
https://ik.imagekit.io/your_imagekit_id/rest-of-the-path.jpg, here is what happens:
rest-of-the-path.jpgis first looked at in our internal caches and storage, i.e., ImageKit.io Media Library. If the image is found, a response is returned. If not:
404response is returned as there are no more image origins configured with this URL-endpoint.
https://ik.imagekit.io/your_imagekit_id. So, if you create new URL endpoints, with different Identifier values, then you would just need to add the identifier in your image URL along with the custom domain name.
ik.imagekit.ioor the ImageKit.io ID no longer appears in the URL.
https://ik.imagekit.io/your_imagekit_id. This is associated with a custom domain
https://images.example.com. So your image URL would become
https://ik.imagekit.io/your_imagekit_id/product-images. This is associated with a custom domain
https://products.example.com. So your image URL would become
https://products.example.com/rest-of-the-path.jpg. Note that with products.example.com, which is mapped to a particular URL endpoint, you do not have to add the endpoint identifier (product-images) in the image URL.