When working with Bright River as an External Post-Production Vendor, you can utilize our Gateway API to send assets between Bright River and Creative Force.

Setting up Bright River using our Gateway API allows seamless communication between the vendor and Creative Force. In this article, we will walk through the steps to add a new vendor using the API method and outline what information will be needed to share and receive from Bright River throughout the process.

To get started, we will need to add a new vendor. Head to Studio Settings → External Post-Production → select Add → then set the Connection Type to 'Gateway API.'

Under Connection Settings, you will need to add a webhook URL– this will effectively be the URL that images are delivered to.

Once you have added the provided URL, click Save.' Creative Force will automatically generate a Secret Key in the field that populates below the Webhook field.

Copy the Secret Key and share it with Bright River so that they may proceed with the necessary configuration on their end. After completing the connection settings configuration, save and exit the vendor setup menu for now.

For the next step, we will need to register a new application in Creative Force. This will allow Bright River to make the necessary API calls to Creative Force to complete the post-production process.

Head to Studio Settings → Registered Apps → 'Register App'

In the pop-up menu, fill out the required configuration fields for the app.

After saving the initial application registration fields, Creative Force will automatically generate an Application ID and a Secret Key. Share these with your Bright River account representative so that they can complete their configuration.

When you have collected the necessary information, you can save and close out of the registration menu.

One final piece of information will be needed in order for Bright River to complete the configuration on their end, and that is the Workspace (Client) ID. The Workspace ID is a unique identifier that exists for each Workspace you've created.

To find it, head to Studio Settings → Workspaces → hover over the desired Workspace → then hit 'Edit.'

The Workspace ID will be listed under the initial Settings tab. Use the paper icon to copy it to your clipboard, then share it with your Bright River contact.

For the final configuration step, we will need to return to the vendor we created earlier under Studio Settings → External Post-Production → 'Edit.'

Move to the 'Specification Settings' tab, where you will be able to configure a number of fields. The information added here will load into your Style Guides when configuring your templates in a later step.

After finishing all of the above setup and configuration, we are now ready to start integrating your new Bright River vendor into your studio productions.

Head to Studio Settings → Workflows → then, in a new or existing Workflow, add the new vendor you created as an option for your Post-Production steps.

For more information on adding and configuring vendors in Workflows, please see our dedicated article on the subject at the link below.

Head into any Style Guides connected to the Workflows you have added the new vendor to. From here, click into the External Post section of the Style Guide for each related Production Type.

Based on the options added in the Specification Settings section of this article, Bright River templates will be available to map as Presets to your photography positions and assets.

There are two types of files that can be sent to Post Production: the main images that need editing, and supporting resource files that are used to aid in the editing of the main image. Resource files might be used for colour accuracy, composites, or ghost mannequin effects.

When sending these different files to Bright River’s system, we will send them in slightly different URL strings so that Bright River will know the purpose of the respective files and which ones to return.

Below is a breakdown of the URL strings based on the type of image that we are sending.

Based on the above logic, Bright River will know which images need to be returned and the purpose of the supporting files.