All Collections
Using BrandKeep
Assets Dashboard
Using the BrandKeep API to Send Files From Your B2B
Using the BrandKeep API to Send Files From Your B2B
Updated over a week ago

With one click, retailers have the ability to send files to BrandKeep with the BrandKeep API. Once sent to BrandKeep they will be associated with the B2B brand you've sent them from.

To obtain the API for a brand in BrandKeep, click on the BrandCard row action menu (1), and select Get API Key (2).

Copy the BrandCard API token and paste it into your B2B.

Sending Files to BrandKeep Using Envoy B2B

Any file that is ready to be picked up on the Downloads dashboard in Envoy B2B can be sent to BrandKeep. To set up the 'send' process you must first copy the API from BrandKeep and add it to the prompt in Envoy.

This is a one-time action, and once complete you can quickly send files to BrandKeep.

Send files to BrandKeep

In Envoy B2B β†’ Downloads dashboard, click on the file's action menu (1) and select Send Files to BrandKeep (2).

If you've previously added the API, you're done. Your file will be in BrandKeep on the assets page and associated with your BrandCard.

Send files to BrandKeep API setup

In Envoy, when you click on Send Files to BrandKeep for the first time you'll be asked for the API key.

Navigate to BrandKeep, then to the BrandCard row action menu (1), and select Get API Key (2).

Copy the BrandCard API token...

...and paste it into the Envoy 'Export Files to BrandKeep' window. Then click Send File.

And that's it. Now anytime you want to send a file to BrandKeep, from the Envoy Downloads dashboard, just click on the Send Files to Brandkeep option.

In BrandKeep, any file that comes straight from Envoy will have 'Envoy B2B' identified as the source.

If your BrandKeep API Key is incorrect in Envoy B2B

If you need to change the BrandKeep API key that you entered into Envoy B2B, head to Settings β†’ Edit Profile.

On the Edit Profile page you'll see the BrandKeep API Key field. Just paste in your new API key here and save the page.


​

Did this answer your question?