Skip to main content

Bynder

Bynder is a digital asset management (DAM) platform where brands store, organize, and distribute approved assets. With the Bynder connector, Nexla can read assets, collections, tags, metaproperties, users, and workflow data, and can update asset metadata, tags, collections, and usage.

Bynder icon

Power end-to-end data operations for your Bynder API with Nexla. Our bi-directional Bynder connector is purpose-built for Bynder, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Bynder or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bynder workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Every Bynder customer has its own portal, and all API calls go to that portal's address. Before creating a credential, note the domain you use to log in to Bynder, such as yourcompany.bynder.com or yourcompany.getbynder.com. Enter only the domain in Nexla: without https:// and without a trailing slash.

Nexla supports two ways to authenticate with Bynder:

  • OAuth 2.0 (Client Credentials) — recommended. Nexla exchanges an OAuth app's client ID and secret for a short-lived access token at https://{portal_domain}/v6/authentication/oauth2/token.

  • Permanent Token — a long-lived token sent as Authorization: Bearer <token>. Bynder started deprecating permanent tokens (and OAuth 1.0) in 2023 and has not yet published a removal date, so use OAuth 2.0 for new setups.

Create an OAuth app in Bynder​

A Bynder administrator creates the OAuth app in the customer's own portal. Nexla cannot provide a shared app, because each portal registers its own.

  1. Log in to your Bynder portal as an administrator, and open Settings > Advanced Settings > Portal Settings > OAuth Apps.

  2. Register a new application, and select Client Credentials as its grant type.

  3. Assign the Bynder user the app will act as. Every API call runs with that user's security roles, so choose a dedicated integration user that can see the assets and data you plan to move.

  4. Select the scopes the app may request. Bynder only grants scopes that match the assigned user's permissions, and the scopes Nexla requests must be a subset of the scopes allowed on the app.

  5. Save the app, and copy its Client ID and Client Secret.

Choose scopes​

The credential's Scopes field defaults to read-only access: asset:read collection:read meta.assetbank:read. That covers the asset, collection, tag, and metaproperty source templates. Add a scope for each other endpoint you plan to use — each template below lists the scope it needs.

Destinations need write scopes

The default scopes cannot write. Before using a destination, add the matching write scope — asset:write, collection:write, meta.assetbank:write, admin.user:write, asset.usage:write, workflow.campaign:write, or workflow.job:write — both to the OAuth app in Bynder and to the credential's Scopes field.

Security roles​

Some endpoints also require a security role on the Bynder user the credential acts as (the user assigned to the OAuth app, or the owner of the permanent token). The templates that need one say so — for example USERMANAGEMENT for users, MEDIAEDIT for updating asset metadata, METAPROPERTYMANAGEMENT for metaproperty options, and CAMPAIGNOVERVIEW, JOBOVERVIEW, CAMPAIGNADD, or JOBADD for workflow campaigns and jobs. A Bynder administrator assigns roles through the user's security profile.

Rate limits​

Bynder allows 4,500 requests in any five-minute window from a single IP address. Requests above that limit are rejected with HTTP 429 Too Many Requests, and the block lifts after five minutes without requests. Large asset exports and per-record destinations count against this limit, so stagger heavy flows that share the same Nexla environment. For details, see Getting Started with the Bynder API.

Authenticate​

Credentials required​

Recommended. Create an OAuth app in your Bynder portal (Settings > Advanced Settings > Portal Settings > OAuth Apps) with the Client Credentials grant type and assign it a user and scopes.

FieldRequiredSecretDescription
Bynder Portal DomainYesNoYour company's Bynder portal domain, without https:// or a trailing slash, e.g. yourcompany.bynder.com or yourcompany.getbynder.com.
Client IDYesNoClient ID of the OAuth app created in your Bynder portal.
Client SecretYesYesClient secret of the OAuth app created in your Bynder portal.
ScopesYesNoSpace-separated OAuth scopes, a subset of those granted to the app. The default covers asset, collection and metaproperty reads; each source/destination names any extra scope it needs.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Select the authentication method — OAuth 2.0 (Client Credentials) or Permanent Token.

  4. Enter your portal domain in the Bynder Portal Domain field, for example yourcompany.bynder.com. Use the domain you log in to, without https://, a trailing slash or an /api suffix.

    Nexla appends paths such as /api/v4/... and /v6/authentication/oauth2/token to this URL. A trailing slash or an added /api produces invalid URLs, and the credential test fails.

  5. For OAuth 2.0 (Client Credentials), enter the values from your Bynder OAuth app:

    • Client ID — the app's client ID.

    • Client Secret — the app's client secret.

    • Scopes — a space-separated list of scopes. Keep the default asset:read collection:read meta.assetbank:read for asset sources, and add write scopes for destinations (see Choose scopes).

    Treat the client secret as a password. Anyone who has it can call the Bynder API with the assigned user's permissions.

  6. For Permanent Token, enter the token in the Permanent Token field. Nexla sends it as Authorization: Bearer <token> on every request.

    Bynder is deprecating permanent tokens. Existing tokens keep working until Bynder announces a sunset date, but new setups should use OAuth 2.0.

  7. Click the Save button at the bottom of the overlay. Nexla tests the credential by calling https://{portal_domain}/api/v4/brands/. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Bynder connector tile, then select the credential that will be used to connect to Bynder, and click Next; or, create a new Bynder credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Bynder endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

100,000-asset cap

Bynder limits page-based asset listing to 100,000 assets (page × limit). The asset templates read up to 100 pages of 1,000 assets and stop there. For larger libraries, split the export by asset type, collection, or tag.

List Assets

Fetch all assets (media) in the portal with their metadata. Bynder caps page-based listing at 100,000 assets (page x limit), so at most 100 pages of 1,000 are read.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records or page 100 is reached.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. Bynder caps page-based asset listing at 100,000 assets (page × limit), so this template reads at most 100 pages of 1,000 assets. To move a larger library, split it into smaller sets with the List Assets by Type, List Assets in Collection, or List Assets by Tag templates. For details, see the Bynder API reference.

Search Assets by Keyword

Fetch assets matching a keyword.

  • Keyword (required): Search term matched against asset name, description, tags and metaproperties.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/?keyword={keyword}, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records or page 100 is reached.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. The 100,000-asset cap on page-based listing also applies here: at most 100 pages of 1,000 matching assets are read. For details, see the Bynder API reference.

List Assets by Type

Fetch assets of one type (image, document, audio or video).

  • Asset Type (required): Asset type to return. Allowed values: image, document, audio, or video. The default is image.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/?type={type}, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records or page 100 is reached.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. The 100,000-asset cap on page-based listing also applies here: at most 100 pages of 1,000 assets of the selected type are read. For details, see the Bynder API reference.

List Assets in Collection

Fetch the assets that belong to one collection.

  • Collection ID (required): ID of the collection. Use the List Collections source to find it.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/?collectionId={collection_id}, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records or page 100 is reached.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. The 100,000-asset cap on page-based listing also applies here. For details, see the Bynder API reference.

List Assets by Tag

Fetch assets carrying at least one of the given tags.

  • Tags (required): Comma-separated list of tags. Use the List Tags source to find them.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/?tags={tags}, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records or page 100 is reached.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. The 100,000-asset cap on page-based listing also applies here. For details, see the Bynder API reference.

Get Asset Download URL

Get a temporary download location for the original file of an asset.

  • Asset ID (required): ID of the asset. Use the List Assets source to find it.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/media/{asset_id}/download/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • The response object is emitted as one record (data path $).

OAuth scope needed: asset:read. The returned location is temporary, so fetch the file soon after the source runs rather than storing the URL for later use. For details, see the Bynder API reference.

List Collections

Fetch all collections visible to the user.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/collections/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: collection:read. For details, see the Bynder API reference.

List Tags

Fetch all tags used on assets.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/tags/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. For details, see the Bynder API reference.

List Metaproperties

Fetch all asset metaproperties (taxonomy fields) with their options. One record per metaproperty.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/metaproperties/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $.*).

OAuth scope needed: meta.assetbank:read. Bynder returns metaproperties as one object keyed by metaproperty name; Nexla emits one record per metaproperty, each including its options. For details, see the Bynder API reference.

List Metaproperty Options

Fetch the options of one metaproperty.

  • Metaproperty ID (required): ID of the metaproperty. Use the List Metaproperties source to find it.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/metaproperties/{metaproperty_id}/options/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: meta.assetbank:read. For details, see the Bynder API reference.

List Metaproperties (Taxonomy API)

Fetch metaproperties through the newer taxonomy API. Requires the meta.assetbank:write scope.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/1/taxonomy/metaproperties, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 1,000 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $.metaproperties[*]).

OAuth scope needed: meta.assetbank:write. Bynder requires the meta.assetbank:write scope for this endpoint even though it only reads data. Add that scope to the credential before using this template. For details, see the Bynder API reference.

List Smartfilters

Fetch all smartfilters.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/smartfilters/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $[*]).

For details, see the Bynder API reference.

List Brands

Fetch all brands and their sub-brands.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/brands/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $[*]).

For details, see the Bynder API reference.

List Users

Fetch all users. Requires the USERMANAGEMENT security role.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/users/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 100 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: admin.user:read. Requires the USERMANAGEMENT security role on the Bynder user the credential acts as. For details, see the Bynder API reference.

Get Current User

Fetch the user the credential acts as.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/currentUser/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • The response object is emitted as one record (data path $).

OAuth scope needed: current.user:read. For details, see the Bynder API reference.

List Security Profiles

Fetch all security profiles (role sets).

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/profiles/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: admin.profile:read. Requires the PERMISSIONMANAGEMENT security role. For details, see the Bynder API reference.

Get Account

Fetch account information for the portal.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/v4/account/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • The response object is emitted as one record (data path $).

For details, see the Bynder API reference.

List User Groups

Fetch all user groups.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/1/groups, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the start and limit query parameters, starting at start 1 with 1,000 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $.items[*]).

Requires the GROUPMANAGEMENT security role. For details, see the Bynder API reference.

List Trashed Assets

Fetch assets removed in the last 30 days.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/trash/media/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 10 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: asset:read. Bynder keeps removed assets in the trash for 30 days, so only assets removed in that window are returned. For details, see the Bynder API reference.

List Workflow Campaigns

Fetch all workflow campaigns. Requires the CAMPAIGNOVERVIEW security role.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/workflow/campaigns/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: workflow.campaign:read. Requires the CAMPAIGNOVERVIEW security role and the Bynder Workflow module. For details, see the Bynder API reference.

List Workflow Jobs

Fetch all workflow jobs. Requires the JOBOVERVIEW security role.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/workflow/jobs/, where {portal_domain} is the portal domain from the credential.
  • Pages are fetched automatically with the page and limit query parameters, starting at page 1 with 100 records per page, until a page returns fewer records.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: workflow.job:read. Requires the JOBOVERVIEW security role and the Bynder Workflow module. For details, see the Bynder API reference.

List Workflow Users

Fetch all workflow users.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/api/workflow/users/, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $[*]).

OAuth scope needed: admin.user:read. Requires the Bynder Workflow module. For details, see the Bynder API reference.

List Webhook Subscriptions

Fetch configured webhook subscriptions.

  • No additional configuration is required beyond selecting this endpoint template.
  • Nexla sends GET requests to https://{portal_domain}/v7/webhooks/public/api/subscriptions, where {portal_domain} is the portal domain from the credential.
  • The endpoint is not paginated; all records are returned in a single request.
  • Each element of the response is emitted as one record (data path $.configs[*]).

OAuth scope needed: webhooks.config:read. The Bynder user needs the View Webhooks configurations or Manage Webhooks configurations role. For details, see the Bynder API reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Bynder data sources can also be manually configured to ingest data from any valid Bynder API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Bynder endpoints live under your portal domain: https://{portal_domain}/api/v4/... and https://{portal_domain}/api/... for most resources, and https://{portal_domain}/v7/... (at the domain root, not under /api) for analytics and webhooks. Most v4 list endpoints return a bare JSON array, so set Path to Data to $[*], and paginate with the page (starting at 1) and limit (up to 1,000) query parameters. The Authorization: Bearer header is added by the credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Bynder data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Bynder destination, and select the Send to Destination option from the menu. Select the Bynder connector from the list of available destination connectors, then select the credential that will be used to connect to Bynder, and click Next; or, create a new Bynder credential for use in this flow.

Before you start

Destinations write to your Bynder portal. The credential needs the write scope listed on each template (the default scopes are read-only), and the Bynder user it acts as needs any security role the template mentions.

How records are sent​

Each destination template sends one request per Nexset record.

  • Form-encoded templates (most v4 endpoints) send each record's top-level fields as form fields. Name the Nexset attributes after the Bynder fields — for example, name and description for a collection.

  • data-field templates — Add Assets to Collection, Add Tag to Assets, and Create Metaproperty Option — expect a single form field named data whose value is a JSON string, such as the text ["id1","id2"]. If the Nexset holds an array or object, add a transform that serializes it to a string in a data attribute.

  • JSON templates (Sync Asset Usage, Create Workflow Campaign, and Create Workflow Job) send the whole record as the JSON request body.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Bynder endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Update Asset Metadata

Update an asset's metadata from each record's fields (e.g. name, description, tags, copyright, archive, metaproperty.<id>). Requires the MEDIAEDIT role.

  • Asset ID (required): ID of the asset to update.
  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/media/{asset_id}/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: asset:write. Each record's top-level fields are sent as form fields, so name the Nexset attributes after the Bynder fields to update, for example name, description, tags, copyright, archive, or metaproperty.<metaproperty_id>. Requires the MEDIAEDIT security role. For details, see the Bynder API reference.

Create User

Create a user from each record (e.g. username, email, firstname, lastname, profileId, password). Requires the USERMANAGEMENT role.

  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/users/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: admin.user:write. Each record's top-level fields are sent as form fields, for example username, email, firstname, lastname, profileId, and password. Requires the USERMANAGEMENT security role. For details, see the Bynder API reference.

Create Collection

Create a collection from each record (name, description).

  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/collections/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: collection:write. Each record's top-level fields are sent as form fields: name (required) and optionally description. For details, see the Bynder API reference.

Add Assets to Collection

Add assets to a collection. Each record needs a 'data' field holding a JSON array of asset IDs as a string, e.g. "["id1","id2"]".

  • Collection ID (required): ID of the collection to add assets to.
  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/collections/{collection_id}/media/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: collection:write. Each record must contain a single data field whose value is a JSON string holding an array of asset IDs, for example the text ["id1","id2"] stored as a string. A record whose data attribute is an actual array is not accepted; use a Nexla transform to serialize the array to a string first. For details, see the Bynder API reference.

Add Tag to Assets

Add a tag to assets. Each record needs a 'data' field holding a JSON array of asset IDs as a string.

  • Tag ID (required): ID of the tag to add.
  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/tags/{tag_id}/media/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: asset:write. Each record must contain a single data field whose value is a JSON string holding an array of asset IDs, for example the text ["id1","id2"] stored as a string. A record whose data attribute is an actual array is not accepted; use a Nexla transform to serialize the array to a string first. For details, see the Bynder API reference.

Remove Tag from Assets

Remove a tag from the listed assets.

  • Tag ID (required): ID of the tag to remove.
  • Asset IDs (required): Comma-separated list of asset IDs to remove the tag from.
  • Nexla sends one DELETE request per record to https://{portal_domain}/api/v4/tags/{tag_id}/media/?deleteIds={asset_ids}.

OAuth scope needed: asset:write. This template sends a DELETE request; the tag and the asset IDs are set on the destination itself, not taken from the records, so each record that flows through repeats the same removal. For details, see the Bynder API reference.

Create Metaproperty Option

Create a metaproperty option. Each record needs a 'data' field holding the option as a JSON string, e.g. {"name":"red","label":"Red"}. Requires the METAPROPERTYMANAGEMENT role.

  • Metaproperty ID (required): ID of the metaproperty to add the option to.
  • Nexla sends one POST request per record to https://{portal_domain}/api/v4/metaproperties/{metaproperty_id}/options/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: meta.assetbank:write. Each record must contain a single data field whose value is the option serialized as a JSON string, for example the text {"name":"red","label":"Red"} stored as a string; use a Nexla transform to serialize the option object to a string first. Requires the METAPROPERTYMANAGEMENT security role. For details, see the Bynder API reference.

Create Asset Usage

Record where an asset is used (integration_id, asset_id, uri, timestamp, additional).

  • Nexla sends one POST request per record to https://{portal_domain}/api/media/usage/.
  • The request body is form-encoded (application/x-www-form-urlencoded).

OAuth scope needed: asset.usage:write. Each record's top-level fields are sent as form fields: integration_id, asset_id, uri, and optionally timestamp and additional. For details, see the Bynder API reference.

Sync Asset Usage

Replace the usage records of an integration (integration_id, uris, usages) as JSON.

  • Nexla sends one POST request per record to https://{portal_domain}/api/media/usage/sync.
  • The request body is JSON (application/json).

OAuth scope needed: asset.usage:write. Each record is sent as the JSON request body and should contain integration_id, uris, and usages. Bynder replaces the integration's existing usage records with the ones sent. For details, see the Bynder API reference.

Create Workflow Campaign

Create a workflow campaign from each record (JSON). Requires the CAMPAIGNADD role.

  • Nexla sends one POST request per record to https://{portal_domain}/api/workflow/campaigns/.
  • The request body is JSON (application/json).

OAuth scope needed: workflow.campaign:write. Each record is sent as the JSON request body describing the campaign. Requires the CAMPAIGNADD security role and the Bynder Workflow module. For details, see the Bynder API reference.

Create Workflow Job

Create a workflow job from each record (JSON). Requires the JOBADD role.

  • Nexla sends one POST request per record to https://{portal_domain}/api/workflow/jobs/.
  • The request body is JSON (application/json).

OAuth scope needed: workflow.job:write. Each record is sent as the JSON request body describing the job. Requires the JOBADD security role and the Bynder Workflow module. For details, see the Bynder API reference.

Manual configuration​

Bynder destinations can also be manually configured to send data to any valid Bynder API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Most Bynder v4 write endpoints accept application/x-www-form-urlencoded bodies, not JSON. Choose the content type that the endpoint's Bynder API reference page lists, and keep the 4,500 requests per five minutes rate limit in mind for large Nexsets.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Bynder endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Bynder endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.