Basic Authentication Error When Automating Artwork Downloads in Business Hub

This article explains why automated artwork downloads that rely on Basic Authentication fail when accessing Business Hub artwork download links, and what authentication behavior is required instead.

Frequently Asked Questions

Why does using Basic Authentication to download artwork from Business Hub result in a failed login redirect?

The Business Hub artwork download endpoint (/bh/production/get_source_artwork/...) does not support Basic Authentication.

When a request is made using Basic Auth credentials, Business Hub does not treat the request as authenticated. As a result, the request is redirected to /user/login with a 302 response.

This commonly affects automated workflows that attempt to download artwork directly using HTTP authentication headers.

Why did this previously work with Basic Authentication?

Earlier behavior allowed artwork download requests to succeed without enforcing an interactive Business Hub login session.

Access controls have since been tightened so that protected Business Hub resources, including artwork files, require a valid authenticated user session.

Does Business Hub support Basic Authentication anywhere?

Basic Authentication is not supported for accessing protected Business Hub pages or downloading artwork files.

Requests authenticated only via Basic Auth headers will be treated as unauthenticated and redirected to the login page.

Does this affect automated downloads?

Yes. Automated or server-to-server workflows that rely on Basic Authentication (for example, Zapier automations or custom scripts) will not be able to download source artwork using the Business Hub download endpoint.

How can source artwork be accessed if Basic Authentication and server-to-server access are not supported?

Accessing source artwork requires:

• A valid Business Hub user
• An active authenticated Business Hub session
• Login-based, interactive authentication

Automated tools and background workflows (for example, Zapier automations) cannot access artwork directly using the Business Hub artwork download endpoint.

Is there a workaround for automated downloads?

A workaround exists using URL-based login parameters, which simulate a user login by passing credentials directly in the request URL.

This involves:

1. Identifying a Business Hub user ID
2. Appending the user ID and password as URL parameters
3. Requesting the artwork download URL with those parameters included

/bh/production/get_source_artwork/{ITEM_ID}?user[id]={USER_ID}&password={PASSWORD}

What should be considered when using URL-based login parameters?

When using this approach, be aware that:

• User credentials are included directly in the URL
• URLs may be logged by browsers, proxies, or automation tools
• URLs may be stored in server logs or third-party services

Appropriate precautions should be taken to limit exposure.

What is the supported way to download source artwork?

The supported method is to:

• Log in to Business Hub as a user
• Download source artwork manually through the Business Hub interface

This ensures access is authenticated correctly.

Why was this behavior changed?

This behavior enforces stricter access controls by ensuring that protected resources cannot be accessed without a valid authenticated session.

Summary

• Source artwork downloads require an authenticated Business Hub session
• Basic Authentication is not supported for Business Hub artwork downloads
• Automated workflows using Basic Auth will fail
• Manual download via Business Hub is supported
• Server-to-server access is not available
• URL-based login parameters can be used to access artwork