Introduction

The Bynder connector allows Simpplr Enterprise Search to index your Bynder digital asset management (DAM) library, making assets and metadata easily discoverable and searchable directly within Simpplr.

With this connector, you can:

• Search media assets (documents, presentations, spreadsheets, and supported file types) with extracted text where supported.

• Respect Bynder access rules in search when document-level security (DLS) is enabled, using portal users, groups, profiles, and metaproperty-based content access.

Indexed content from Simpplr Enterprise Search is available in:

• Main search listing

• Smart answers (where your tenant enables it and content is eligible)

Capabilities at a glance

Objects and content supported

1. Objects - The connector indexes Bynder media assets (files in the asset bank), including common types such as:

• Documents (e.g. PDF, Word, PowerPoint, Excel, text, HTML, CSV)

2. Not Indexed

• Collections

• Archived assets

• Workflow jobs, Brandstore orders, analytics, webhooks, and other non-media entities

• Body text for unsupported file extensions (metadata is still indexed; see Known limitations)

3. Metadata - For each indexed item, Bynder Connector captures:

• Title

• Description

• Author Name

• Timestamps: created_at, updated_at, date_published, _timestamp

• Location / taxonomy: brand_id, asset_type (Bynder type), custom metaproperty fields

• Extension

• File Size

4. Permissions model - Permissions are read from Metaproperties assigned to the Bynder asset and enforced in Simpplr Enterprise Search.

Versions and Editions Supported

Prerequisites

Before you begin, ensure the following:

1. Source system permissions

• You can administer Bynder (or work with your Bynder admin) to create an OAuth client and grant API scopes.

• The account used to approve/consent the integration can access the assets and users you intend to index.

• Why needed: Bynder only returns data the token and user are allowed to see.

2. Application / service account

• Ability to create an OAuth 2.0 client (client ID + client secret) in Bynder.

• Ability to assign scopes: admin.user:read, asset:read, meta.assetbank:read.

• Why needed: Authentication and API access for media, users and metaproperties access.

3. Network and firewall

• Outbound HTTPS from the Simpplr Enterprise Search connector runtime to your Bynder hostname (e.g. https://company.bynder.com).

• Allow traffic to Bynder APIs and to CDN/download URLs returned for file extraction (asset downloads).

Authentication and security

1. Authentication mechanism - Simpplr Enterprise Search connects to Bynder using OAuth 2.0 client credentials:

• Auth type: OAuth 2.0 client credentials (Bearer token)

• Token endpoint: {domain}/v6/authentication/oauth2/token

• Scopes or permissions required (examples):

2. Token behavior:
   Tokens are refreshed automatically before expiry (about 60 seconds before expires_in). On 401 from API calls, the connector refreshes the token and retries once.

3. Data security

• Data storage and residency: Indexed content and metadata are stored in your Simpplr Enterprise Search index region (per your Simpplr deployment).

• Encryption in transit: Server-side encryption with Amazon S3 managed keys (SSE-S3), TLS encryption in Kafka.

• Encryption at rest: TLS for all Bynder API and download traffic. 

• Permission enforcement: queries filter results using synced user principals (email, user, profile, group) and per-asset allowaccess_control.

Setup and configuration

Step 1 - Prepare Bynder

1. Sign in to the Bynder admin / developer area for your portal.

2. Create an OAuth 2.0 client (client credentials).

3. Grant scopes: admin.user:read, asset:read, meta.assetbank:read.

4. Ensure the client can use Content Access APIs if you plan to enable DLS.

5. Copy Client ID and Client secret.

6. Note your portal domain (e.g. company.bynder.com or full https://company.bynder.com).

Step 2 - Create the connector in Simpplr Enterprise Search

1. In Simpplr, go to: Enterprise Search → Connectors → Add connector.

   

2. Select Bynder.

   

3. Enter basic information:

   • Name: Name for the Bynder connector

   • Domain: Bynder portal hostname or URL

   • Client ID

   • Client Secret
     

4. Save the configuration.

Step 3 - Filters (Optional)

1. Advanced rule

age — ISO timestamp; only assets modified on or after that time are included (maps to Bynder dateModified).

2. Audience based filtering.

   1. Include audiences

   2. Exclude audiences

Step 4 - Monitor

1. After saving the connector configuration, the initial sync starts automatically.

2. Monitor sync status at: Enterprise Search > Connectors > Bynder > Health.

3. Available sync schedule:

Crawling and sync behavior

Describe how the connector works over time:

1.  Initial full crawl

• Indexes media assets with pagination (page size 300).

• Applies 730-day dateModified cutoff unless sync from timestamp is set.

• Skips archived assets on full sync.

• Extracts file content for supported extensions (doc, docx, pdf, ppt, pptx, xls, xlsx, csv, txt, rtf, html, odt, etc.).

• Duration depends on asset count, file sizes, and API rate limits.

2. Incremental updates

• Mechanism: Timestamp Cursor

• Frequency: Hourly

3. ACL sync

• Mechanism: Information about all the active users is ingested.

• Frequency: Daily

4. Deletion and permission changes

• Deleted / trashed / archived: removed from the index on incremental sync (OP_DELETE).

• Permission changes: updated when the asset is re-fetched; user ACL changes apply after access control sync.

5. Expected latency

• Under normal load, changes typically appear within 1–2 hours after modification in Bynder, depending on job queue and volume.

• Large backfills or API 429 throttling can extend delay.

Field mapping and search experience

1. Default field mapping

Source field Bynder → Stored Field Simpplr

2.  Search experience - how content from this connector appears in search:

• Result layout:

  • Icon: Bynder icon

  • Source label: "Bynder Connector Name"

  • Title: Asset title as a clickable link to the original asset in Bynder

  • Snippet: Excerpt from the body

  • Last modified date: When the article was last updated

• Available filters and facets:

  • Source =Bynder

  • File type

  • Last modified

  

• Participation in advanced features:

  • Smart Answers / Q&A: Yes

  • Semantic / hybrid ranking: Yes

Known Limitations

Monitoring and troubleshooting

Connector health and monitoring

• Enterprise Search → Connector name → Health / sync history

Common issues and resolutions

Issue: Authentication failed

Issue: Incremental sync failed — cursor empty

Issue: Rate limit or API errors (429 / 5xx)

When to contact support 

1. Authentication error persists even after trying the above-mentioned resolutions

2. Sync is stuck and hasn’t progressed in a few hours,

3. Sync failure

4. Incomplete or Partial sync.

5. DLS results clearly disagree with Bynder portal for many users

6. Missing file body in search

When contacting Support, include:

• Connector name and instance ID (if available)

• Organization URL

• Approximate time and date of the issue

• Error messages or screenshots

Steps you already tried

Frequently asked questions (FAQ)

Q. Can I connect multiple {{SourceSystem}} tenants or domains?
Ans. Yes — create one connector instance per Bynder portal (domain + OAuth client).

Q. How often does Bynder Connector sync data?
Ans. The connector runs a full crawl on first setup and then there is Incremental sync for every 1 hour 

Q. Are comments, revisions, or version history indexed?
Ans. No — current scope is media assets and metadata from the media API, not version history or comments.

Q. Does the connector index content from external guests or shared links?
Ans. Only what the OAuth app can read via Bynder APIs. Ad-hoc external sharing outside API visibility is not indexed.

Q. What happens when a user loses access to an item in Bynder?
Ans. On incremental sync, asset ACL and deletes are updated; access control sync refreshes user principals. Search results should reflect changes within the usual 1–2 hour window under normal load.

Q. Can I exclude certain sites/teams/folders from being indexed?
Ans. There is no folder/library picker; indexing is tenant-wide for visible media.

Q. How are deletions handled?
Ans. Trashed assets (trash API by dateRemoved) and archived assets are removed from the index on incremental sync. Permanent removal in Bynder should align with trash/archive behavior above.