> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/bynder.md).

# Bynder

Set up the Bynder connector in Pandium using your portal URL and OAuth credentials so tenants can securely sync digital assets, metadata, and collections, and receive asset webhooks.

## **Connector Overview**

<figure><img src="https://4017407078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MfJn-9R_dn6dvcGNcdk%2Fuploads%2Fgit-blob-83c7ba09f6dcfed449d9123abe70b43b380d58f4%2Fbynder-logo.png?alt=media" alt="" width="200"><figcaption></figcaption></figure>

Bynder is a digital asset management (DAM) platform that helps brands store, organize, enrich, and distribute their creative content from a single portal.

## **Authentication Type**

OAuth2

## **Webhook Supported**

Yes

## **Secrets**

* PAN\_SEC\_BYNDER\_ACCESS\_TOKEN
* PAN\_SEC\_BYNDER\_REFRESH\_TOKEN
* PAN\_SEC\_BYNDER\_TOKEN\_TYPE
* PAN\_SEC\_BYNDER\_EXPIRES\_AT
* PAN\_SEC\_BYNDER\_EXPIRES\_IN
* PAN\_SEC\_BYNDER\_SCOPE
* PAN\_SEC\_BYNDER\_API\_BASE\_URL

## **API Client Supported**

No

## **Requirements for Provisioning**

In order to provision your connector, the following Bynder information must be gathered:

* Portal URL
* Client ID
* Client Secret
* Scopes
* Webhook Events (optional)
* Pre-Archived Notification Days (optional)

To obtain the information required for setting up your Bynder Connector, perform the following steps:

1. For Portal URL
   1. Every Bynder customer has their own portal, for example `https://your-company.bynder.com`. Enter that URL with no trailing slash. The OAuth app, the API, and the webhook subscriptions all live on this host.
2. For Client ID and Client Secret
   1. Log in to your Bynder portal as an admin.
   2. Go to **Settings > Advanced Settings > Portal settings > OAuth Apps** and create a new OAuth app using the Authorization Code grant.
   3. Enter the Pandium [redirect URL](/connectors/connectors-101.md#redirect-urls) for your environment.
   4. Grant the app every scope you plan to select in Pandium. Bynder rejects the connection if Pandium asks for a scope the app was not granted.
   5. Copy the Client ID and Client Secret.
3. For Scopes
   1. Select the scopes your integration needs. Always include **Offline (refresh token)**; without it Bynder does not issue a refresh token and the connection expires after one hour.
   2. Include **Current User Read**. Pandium calls `/api/v4/currentUser/` to verify the connection and identify the connected user.
   3. Include both **Webhooks Config Read** and **Webhooks Config Write** if you select any Webhook Events.
4. For Webhook Events
   1. Select the asset, workflow, antivirus, or DAT events your integration should receive. Pandium creates the webhook subscription in your portal when a tenant connects and removes it when the tenant disconnects.
   2. **Pre-Archived Notification Days** only applies to the **Asset Pre-Archived** event. It sets how many days before archival Bynder sends the notification (minimum 1).
   3. Bynder allows at most 10 webhook configurations per portal, and each connected tenant uses one.

## **API Resources**

For more information on how to utilize the Bynder API, feel free to reference the following [documentation](https://api.bynder.com/reference).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandium.com/connectors/connectors-101/bynder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.