1. General Information
Bynder is a leading SaaS-based Digital Asset Management (DAM) platform founded in 2013 in Amsterdam, designed to help brands centralize, manage, and distribute their digital content efficiently. It is widely used by global enterprises, including 20% of Fortune 500 companies, serving over 1.7 million users across 4,000+ brands worldwide.
2. Connect Bynder to OneTeg
Bynder utilizes OAuth 2.0 protocol to authenticate its APIs. To authorize API requests via OAuth 2.0, it is necessary to create a client within the Bynder portal.
Bynder App and Token Creation
Access the Portal Settings by navigating to your user menu and selecting Additional Settings.
Navigate to Portal Settings and access the OAuth Apps section to create a new application or retrieve existing ones.
Please either create a new OAuth App or utilize an existing one. The Client ID and Client Secret credentials will be required for establishing the OneTeg connection.
3. Connection Settings and Configuration for OneTeg
|
Settings Parameters |
Value |
Description |
Required (Y/N) |
|---|---|---|---|
|
Connection Name |
Bynder Connection |
Preferred Connection Designation |
Y |
|
Connector |
bynderConnector-v1.1 |
Preferred Connector Designation |
Y |
|
Endpoint URL |
<Bynder URL> |
Endpoint required for performing CRUD |
Y |
|
Authentication |
OAuth |
Type of Authentication |
Y |
|
Flows |
Authorization Code |
Type of Authentication |
Y |
|
Client ID |
<Client ID> |
Client ID from Bynder App |
Y |
|
Client Secret |
<Client Secret> |
Client Secret from Bynder App |
Y |
|
Token URL |
https://<BynderURL>/v6/authentication/oauth2/token |
Token process URL |
Y |
|
Authorization Url |
https://<BynderURL>/v6/authentication/oauth2/auth |
Authorization URL |
Y |
|
Scopes |
asset:read asset:write collection:read |
Define access required for connector |
Y |
4. Supported Bynder Actions and Options