DXM + Bynder

Generate more on-brand content from trusted assets.

The DXM + Bynder integration connects trusted DAM assets to DXM’s AI creative production workflow. Users can select approved images and videos from Bynder through Universal Compact View, import them into DXM, and use them as source references for new branded outputs.

DXM preserves the Bynder asset ID, source metadata, available usage information, rights-related context, and provenance, so generated work stays traceable to its original assets. After review, approved DXM outputs can be exported back to Bynder as new assets for centralized storage, management, and distribution.

How It Works

DXM connects to a customer’s Bynder portal so users can browse approved Bynder assets from inside DXM, import selected image and video assets into the DXM media library, preserve Bynder source metadata/provenance, and export finished DXM assets back to Bynder.

Bynder Features Used

Universal Compact View: Used for the in-app Bynder picker during Media Library import.

API: Used for OAuth token exchange, brand lookup, asset detail, usage, metaproperties, download fallback, and upload/export.

DXM Web App / UI

DXM provides the integration UI for connecting/managing Bynder, importing from Bynder, generating visual media, exporting to Bynder, and choosing the destination brand.

OAuth Scope

asset:read: Read asset details and import/download selected assets.
asset:write: Upload/export DXM assets to Bynder.
asset.usage:read: Read Bynder asset usage during import.
collection:read: Read collection context on imported assets.
meta.assetbank:read: Read metaproperty definitions and resolve metadata/rights fields.

Bynder Admin Setup

Instructions for configuring the Bynder integration.

1. In Bynder, go to Settings.

6. Create the Oauth app with these values:
Application name: DXM
Homepage URL: https://www.dxmdesigner.com
Application description: DXM imports assets from Bynder into the gallery and exports DXM assets back to Bynder.
Integration: Other
Integration name: DXM
Grant type: Client Credentials
Assigned user: Cathy Clarke

2. Open Advanced Settings.

7. Select only these OAuth scopes:
asset:read
asset:write
asset.usage:read
collection:read
meta.assetbank:read

3. Open Portal Settings.

8. Save the OAuth app

4. Open OAuth apps.

9. Copy the Client ID and Client Secret. These will be entered into DXM.

5. Click Add new app.

DXM Admin Setup

Instructions for configuring the DXM integration.

1. In DXM, open Settings > Integrations

6. Save the connection.

2. Select Bynder

7. DXM validates the connection by exchanging an OAuth client credentials token and fetching available Bynder brands.

3. Click COnnect Bynder.

8. If the portal has multiple brands, choose the default export brand.

4. Enter the Bynder portal URL, for example: example.getbynder.com

9. DXM stores the client secret encrypted. Access tokens are fetched as needed and are not stored.

5. Enter the OAuth Client ID and Client Secret from the Bynder OAuth app.

Importing Assets From Bynder

Instructions for importing existing assets from Bynder DAM to DXM.

1. In DXM, open Media Library.

5. The user selects one or more image or video assets.

2. Click Import.

6. DXM copies the selected files into DXM/R2 storage.

3. Choose Bynder.

7. DXM stores the Bynder asset ID, source metadata, rights/provenance, usage context, metaproperty-derived fields, and collection context when available.

4. DXM opens Bynder Universal Compact View inside the DXM interface.

8. DXM skips duplicates by Bynder asset ID.

Exporting Assets to Bynder

Instructions for exporting new assets from DXM to Bynder DAM..

1.. In DXM, open Media Library.

4. Select the destination Bynder brand.

2. Select one or more DXM assets.

5 DXM uploads the asset using Bynder multipart upload.

DXM Style Design lets designers define and lock in brand styles

6. DXM saves the uploaded asset into the selected Bynder brand.

For Bynder Customers

Integration FAQ

The DXM + Bynder integration lets approved users select image and video assets from Bynder, import copies into DXM, and preserve source identity, metadata, and rights/provenance information for use in DXM media workflows.

What this integration does:

• Browse/select assets from Bynder
• Import image and video assets into DXM
• Preserve Bynder source identity and relevant metadata
• Store a DXM-controlled copy for use in the DXM media library
• Export or deliver DXM-created assets, only if that is part of the enabled workflow

What this integration does not do yet:

• No continuous sync
• No Bynder webhook/event automation
• No Bynder Asset Tracker integration
• No metaproperty write-back
• No replacement of Bynder as the system of record

Q&A:

Q: Who should use this integration?

A: Creative and marketing teams that already manage approved assets in Bynder and want to use those assets inside DXM workflows without manually downloading and re-uploading files.

Q: Does importing from Bynder modify the original Bynder asset?

A: No. Importing reads the selected asset and copies it into DXM. The original Bynder asset is not modified.

Q: What permissions are required in Bynder?

A: The Bynder user must have access to the assets they want to select and the permissions required by the configured OAuth scopes. Availability may also depend on the customer’s Bynder portal configuration.

Q: Does DXM store Bynder credentials?

A. DXM does not store Bynder user passwords. DXM stores the portal connection details required for the integration, and client secrets are encrypted. DXM does not persist Bynder access tokens.

Q: Will changes in Bynder update assets already imported into DXM?

A: Not automatically. Imported assets are copied into DXM. If the source asset changes in Bynder, the user must re-import it unless a future sync workflow is enabled.

Q: Will deleting an asset in Bynder delete it from DXM?

A: No. Because DXM stores an imported copy, deleting or changing the original Bynder asset does not automatically remove the DXM copy.

Q: Q: Does the integration bypass our Bynder approval workflow?

A: No. DXM imports assets the user is authorized to access. It does not change Bynder approvals, permissions, or governance rules.

Q: What asset types are supported?

A. DXM supports importing image and video assets.

Q: Where are imported assets stored?

A: Imported assets are stored in DXM-controlled storage so they remain available in the DXM media library. DXM also preserves source information for traceability.

Q: Does DXM continuously sync with Bynder?

A: No. The current integration is user-initiated import/export. There is no continuous sync.

Q: Does DXM support Bynder webhooks or event-based sync?

A. Not in the current release. Import and export actions are user-initiated. DXM does not currently listen for Bynder asset changes, approvals, or publish events.

Q: Does DXM report usage back to Bynder Asset Tracker?

A: No, not currently. Not currently. DXM preserves rights, source, and provenance metadata internally, but it does not currently write usage events back to Bynder Asset Tracker.

Q: Does DXM use a Bynder SDK?

A: No. DXM uses Bynder Universal Compact View and Bynder REST APIs directly.

Q: What metadata does DXM preserve?

A: DXM preserves source identity and relevant metadata used for provenance, rights, and search. Exact fields may vary by portal configuration and enabled metaproperties.

Q: Does DXM write metaproperties back to Bynder?

A: DXM can read selected Bynder metaproperties to help resolve metadata, rights, and provenance fields. DXM does not currently write metaproperty changes back to Bynder.

Q: Is DXM only referencing Bynder CDN URLs?

A: No. DXM copies imported assets into DXM-controlled storage so they remain available in the DXM media library. Bynder source identity and metadata are preserved for provenance.