BigCommerce

BigCommerce API Image Uploads: A Developer's Guide to Public URLs and Deprecation Clarifications

In the fast-paced world of e-commerce, maintaining a compelling and accurate product catalog is non-negotiable. For BigCommerce merchants, leveraging the platform's robust API is often the cornerstone of efficient operations, enabling automation for tasks like product creation, inventory synchronization, and critically, managing product images. However, system notifications and evolving features can sometimes lead to confusion, potentially disrupting vital automated workflows.

Code example demonstrating a BigCommerce API request for adding a product image using a public URL.
Code example demonstrating a BigCommerce API request for adding a product image using a public URL.

Navigating the Confusion: API Image Uploads vs. Browser-Based Editing Deprecation

A recent discussion on the BigCommerce community forum brought to light a common point of misunderstanding that many developers and merchants might encounter. A user reported difficulties with product images not being added correctly via the API when using public URLs for new products. This concern was exacerbated by a BigCommerce notification stating:

“We are disabling the 3rd-party integration for browser-based image editing as a result of an increased number of issues reported by merchants, as well as having confirmed that the vendor is deprecating the product. We are looking at alternatives to bring back this feature. You can still upload your images directly to the image manager.”

Naturally, this message led to questions: Does this deprecation of a "3rd-party integration for browser-based image editing" also impact the API's ability to fetch images from public URLs? For businesses relying on automated product data synchronization, this ambiguity could signal a significant hurdle.

Clarifying the Functionality: API Remains Robust for Public URLs

Fortunately, the answer is clear and reassuring: the BigCommerce API's capability for uploading product images via public URLs remains fully functional and unaffected by the browser-based editing deprecation notice. The key distinction lies in understanding that the deprecated feature was a specific browser-based image editing tool, not the core API functionality for image ingestion.

As experts in BigCommerce migrations and integrations, we at Big Migration understand the critical importance of reliable API functionality for seamless data transfer and ongoing store management. The Product Images API is a powerful tool for automating the addition and management of product visuals, crucial for maintaining an engaging storefront and streamlining large-scale data operations, especially during a platform migration.

Deep Dive: Mastering the BigCommerce Product Images API

To ensure successful image uploads using public URLs, developers should focus on the dedicated Product Images API endpoint and adhere to best practices. This approach guarantees that your automated processes, whether for daily updates or a full-scale BigCommerce migration, run smoothly.

The Correct Endpoint and Request Structure

The BigCommerce API provides a specific endpoint for managing product images, separate from the main product creation endpoint. This separation allows for more granular control and better performance.

  • Endpoint: /v3/catalog/products/{product_id}/images
  • Method: POST (for adding new images)
  • Content-Type: application/json

When sending your request, the body should include the image_url property pointing to your publicly accessible image. Here’s an example of a typical API request body:

{
"image_url": "https://yourdomain.com/path/to/your/image.jpg",
"is_thumbnail": false,
"sort_order": 0,
"description": "Product image description"
}

It's crucial to send this request to the dedicated Product Images endpoint after the product itself has been created, obtaining its product_id. Attempting to include images directly within the initial product creation request (/v3/catalog/products) when using public URLs is not the recommended or supported method for this specific scenario.

Key Considerations for Successful Image Uploads

To prevent common issues and ensure your images are processed correctly, keep the following technical checks in mind:

  • Public Accessibility: The image_url must point to an image that is directly accessible from the internet. This means no authentication, no redirects, and no firewalls blocking access from BigCommerce's servers.
  • File Size Limit: Each image must be under 8MB. Larger images will fail to upload and should be optimized before being linked.
  • Supported Formats: BigCommerce supports a range of image formats including JPEG, PNG, GIF, BMP, and WEBP. Ensure your source images are in one of these formats.
  • Dedicated Endpoint: Always use the /v3/catalog/products/{product_id}/images endpoint for adding images, rather than trying to embed image data or URLs within the main product creation request.
  • JSON Formatting: Confirm your API request is sent with the Content-Type: application/json header and that the request body is valid JSON.

Why This Matters for Your E-commerce Business and Migrations

For any e-commerce business, especially those undergoing a platform migration or managing a large, frequently updated catalog, efficient image handling through the API offers significant advantages:

  • Automation & Scalability: Automating image uploads saves countless hours, reduces manual errors, and allows for rapid product catalog expansion without human intervention. This is invaluable during a BigCommerce migration where thousands of products might need to be imported.
  • Data Integrity: By programmatically linking images from a reliable source (like a CDN or existing asset library), you ensure consistency and accuracy across your product listings.
  • Faster Migrations: During a BigCommerce migration, the ability to programmatically import product images via URLs drastically speeds up the process, ensuring your new store is visually complete from day one. Big Migration specializes in leveraging these API capabilities to ensure a smooth, efficient transition.
  • Dynamic Content: For stores with dynamic product offerings or user-generated content, the API provides the flexibility to update images on the fly, keeping your storefront fresh and relevant.

Troubleshooting Common Issues

If you encounter issues despite following the guidelines, consider these troubleshooting steps:

  • Verify URL: Double-check the image_url for typos, correct protocol (HTTP/HTTPS), and ensure it resolves correctly in a browser.
  • Test Accessibility: Use a tool like curl or an online URL checker to confirm the image can be accessed externally without authentication.
  • Check Server Logs: If the image is hosted on your own server, review its access logs to see if BigCommerce's servers attempted to fetch the image and if any errors occurred.
  • API Response: Examine the full API response for detailed error messages, which often provide clues about what went wrong.
  • Consult BigCommerce Documentation: The official BigCommerce Developer Documentation is an invaluable resource for the latest API specifications and troubleshooting guides.

Partner with Big Migration for Seamless BigCommerce Integrations

Understanding and effectively utilizing the BigCommerce API is crucial for optimizing your e-commerce operations and ensuring successful platform migrations. While the platform evolves, core functionalities like API-driven image uploads remain robust.

At Big Migration, we specialize in helping businesses navigate the complexities of BigCommerce, from custom API integrations to comprehensive store migrations. If you're facing challenges with product data synchronization, image management, or planning a move to BigCommerce, our team of experts is ready to provide tailored solutions and ensure your e-commerce platform performs at its peak.

Share:

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools