Connect Bynder to Caimera

Connecting your Bynder portal lets you save Caimera generations straight into Bynder as new assets, and browse your Bynder library from inside Caimera when picking reference images.

Bynder has no marketplace app, so each portal registers its own OAuth application. A Bynder portal admin does this once, then anyone in your Caimera workspace can use the connection.

Before you start

• You need admin access to your Bynder portal (specifically, access to Portal settings → OAuth Apps).
• Bynder must be enabled on your Caimera workspace. If you don't see Save to Bynder in the download menu, ask your Caimera contact to switch it on.

Step 1 — Register the OAuth app in Bynder

In your Bynder portal, go to Settings → Advanced settings → Portal settings → OAuth Apps and create a new application with these values:

A few of these matter more than they look:

• Integration type must include the refresh token. Without it, the connection stops working after about an hour and everyone has to reconnect.
• Redirect URL has to match exactly — same scheme, host and path, no trailing slash. A mismatch shows up as an error on Bynder's authorize screen.
• CORS access control allowlists Caimera's domain for browser-side calls to your portal. Set it to the domain you use Caimera on.
• Scopes — tick asset:read, asset:write and current.user:read. Caimera requests exactly these, plus offline access for the refresh token, and nothing more. Leaving one out fails the authorization step, so all three need to be enabled.

If your team uses Caimera on a different domain, use that domain in place of https://app.caimera.ai in both the CORS and redirect fields. The Caimera connect dialog always shows the exact values for the site you're on — copy them from there if in doubt.

Save the app, then copy its Client ID and Client secret. Bynder shows the secret once, so keep it to hand for the next step.

Step 2 — Connect from Caimera

1. In Caimera, open any generation and choose Download → Save to Bynder (or use the save menu on a library selection).
2. The Connect Bynder dialog appears. Fill in:

• Portal domain — your Bynder hostname only, e.g. your-brand.bynder.com (no https://, no trailing slash).
• Client ID and Client secret — from Step 1.

3. Click Connect. Bynder's authorization screen opens in a new tab; approve access.
4. You'll land on a "Bynder connected" confirmation. Close that tab and return to Caimera — the connection is live for the whole workspace.

Retry the save and the image uploads to Bynder.

What you can do once connected

• Save generations to Bynder — single images or a multi-select from your library. You can choose the file format (PNG, JPEG, TIFF, PSD or SVG where available) before saving; Caimera produces the same file a local download would.
• Import from Bynder — the Bynder tab in Caimera's image picker opens Bynder's own asset browser. It asks each person to sign in to your portal the first time they use it, then they can search and pull assets in as references.

New assets land in your portal's default brand and appear in Bynder's regular upload/approval flow, so your existing metadata and permissions rules apply as normal.

Reconnecting and troubleshooting

"Reconnect Bynder" or a save that asks for credentials again. Bynder's access was revoked, the OAuth app was edited, or the refresh token expired. Re-enter the details in the Connect Bynder dialog to restore it. If it keeps happening, check the app's integration type still includes Refresh Token.

Error on Bynder's authorize screen. Almost always the redirect URL. Compare the app's Redirect URL character-for-character with the one shown in the Caimera dialog.

"Could not start Bynder connection." Usually the portal domain. It must be the bare hostname — your-brand.bynder.com, not a full URL or a login page link.

Save fails with a permissions error. Confirm the OAuth app has all three scopes, and that the Bynder user who approved the connection is allowed to upload to the target brand.

The Bynder tab in the picker won't load. Check your Caimera domain is in the app's CORS access control field, and that your portal allows the compact view to be embedded.

If something still doesn't work, contact Caimera support with your portal domain and roughly when the attempt happened.

Updated on: 30/07/2026