Webdam

Webdam is a cloud-based digital asset management (DAM) platform that helps organizations centralize, organize, and distribute their digital content, including images, videos, and documents, enabling efficient brand management and content collaboration.

Power end-to-end data operations for your Webdam API with Nexla. Our bi-directional Webdam connector is purpose-built for Webdam, 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 Webdam or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Webdam 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

Before creating a Webdam credential, you need to obtain your Client ID and Client Secret from your Webdam Developer account. Webdam uses OAuth2 (3-legged) authentication for all API requests.

To obtain your Webdam OAuth credentials, follow these steps:

1. Sign in to your Webdam account using your administrator credentials.

2. Navigate to the Webdam Developer Portal or visit the Webdam API documentation to access API key management.

3. In the Webdam Developer Portal or API settings, navigate to API Keys, OAuth Applications, or Developer Settings to access your OAuth application management.

4. If you don't have an OAuth application yet, click Create Application or Register Application to create a new OAuth application.

5. Configure your OAuth application settings:

   • Enter a name for the application (e.g., "Nexla Integration")
   • Review and accept the Webdam API Terms of Service
   • Set the application type to OAuth2 or 3-legged OAuth
   • Configure the redirect URI if required
   • Click Create or Register to create the application

6. After the application is created, you will see your Client ID and Client Secret. Copy both values immediately, as the Client Secret may not be accessible again after you navigate away from the page.

7. Store both credentials securely, as you will need them to configure your Nexla credential. The Client Secret is sensitive information and should be kept confidential.

The Client ID and Client Secret are used in the OAuth2 (3-legged) authentication flow to obtain access tokens. During the OAuth flow, you will be redirected to Webdam to authorize Nexla to access your Webdam account. After authorization, Nexla will automatically obtain and store the access tokens needed to authenticate API requests. If your credentials are compromised, you should immediately revoke them in your Webdam Developer Portal and generate new ones. For detailed information about obtaining OAuth credentials, API authentication, and available endpoints, refer to the Webdam API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	Yes	Webdam Client ID
Client Secret	Yes	Yes	Webdam Client Secret for Token URL

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.

New Credential Overlay – Webdam

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

3. Enter your Client ID in the Client ID field. This is the OAuth2 client identifier you obtained from your Webdam Developer Portal (API Keys or OAuth Applications). The Client ID is used to identify your application when requesting access tokens.

4. The OAuth2 authentication flow will be initiated when you save the credential. During the OAuth flow, you will be redirected to Webdam to authorize Nexla to access your Webdam account.

5. After authorization, Nexla will automatically obtain and store the access tokens needed to authenticate API requests.

   Your Webdam OAuth credentials (Client ID, Client Secret) can be found in the Webdam Developer Portal or your Webdam Developer Portal under API Keys or OAuth Applications. The Client Secret is sensitive information and must be kept confidential.

   If your credentials are compromised, you should immediately revoke them in your Webdam Developer Portal and generate new ones. The OAuth credentials provide access to your Webdam account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about obtaining OAuth credentials, API authentication, and available endpoints, see the Webdam API documentation.

6. Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

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 Webdam connector tile, then select the credential that will be used to connect to the Webdam instance, and click Next; or, create a new Webdam 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 Webdam 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.

Search Assets

This endpoint template searches assets in DAM by text from your Webdam account. Use this template when you need to search for assets, filter assets by criteria, or retrieve asset metadata based on search queries for analysis, reporting, or integration purposes.

• Select the Sort Order from the Sort Order pulldown menu. This should be the sort order value that determines how search results will be sorted. You can select from the available options: asc (ascending order) or desc (descending order). The default value is asc.
• Select the Sort By Value from the Sort By Value pulldown menu. This should be the field to sort the assets. You can select from the available options: filename (File name), filesize (File size), datecreated (Created date of assets), or datemodified (Modified date of assets). The default value is filename.
• Enter the Text to query in the Text to query field. This should be the search text that will be used to search for assets. The Text to query determines which assets will be retrieved based on the search criteria.
• Enter the Folder ID in the Folder ID field. This should be the folder ID that limits the search to a specific folder. The Folder ID determines which folder's assets will be searched.

This endpoint searches assets in DAM by text from your Webdam account, including asset IDs, filenames, metadata, and other asset information. The endpoint uses offset-based pagination to handle large result sets efficiently. Nexla will automatically follow the pagination to fetch subsequent pages of search results.

For detailed information about asset search, API response structures, pagination, and available asset data, see the Webdam API documentation.

Get resources

This endpoint template gets resources from your Webdam account. Use this template when you need to access resource information, resource details, or resource metadata for analysis, reporting, or integration purposes.

• Enter the Resource Type in the Resource Type field. This should be the type of resource you want to retrieve (e.g., folders, assets, etc.). The Resource Type determines which type of resources will be retrieved.

This endpoint gets resources from your Webdam account, including resource IDs, names, metadata, and other resource information. The endpoint retrieves resources based on the specified resource type.

For detailed information about resources, API response structures, and available resource data, see the Webdam API documentation.

Download Asset

This endpoint template downloads an asset from your Webdam account. Use this template when you need to download asset files, retrieve asset content, or access asset binary data for analysis, reporting, or integration purposes.

• Enter the Asset ID in the Asset ID field. This should be the unique identifier of the asset you want to download. The Asset ID determines which asset will be downloaded.

This endpoint downloads an asset from your Webdam account, including the asset file content and metadata. The endpoint retrieves the asset file based on the specified asset ID.

For detailed information about asset downloads, API response structures, and available asset data, see the Webdam API documentation.

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

Webdam data sources can also be manually configured to ingest data from any valid Webdam 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.

Webdam API endpoints typically follow the pattern https://apiv2.webdamdb.com/{endpoint_path}. The endpoint requires OAuth2 authentication, which is handled automatically by your credential configuration.

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 Webdam 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 Webdam destination, and select the Send to Destination option from the menu. Select the Webdam connector from the list of available destination connectors, then select the credential that will be used to connect to the Webdam instance, and click Next; or, create a new Webdam credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Webdam 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.

Create Resources

This endpoint template creates resources in your Webdam account. Use this template when you need to automatically create resources (such as folders, lightboxes, or other resource types) based on data from your Nexla flows.

• Enter the Resource Type in the Resource Type field. This should be the type of resource you want to create (e.g., folders, lightboxes, etc.). The Resource Type determines which type of resources will be created.
• This endpoint sends data as JSON in the request body to create new resources. Each record from your Nexset will be sent as a separate API request to create a resource. The request body should contain the resource data in the format required by the Webdam API, including all required properties for resource creation.

This endpoint sends data as JSON in the request body to create new resources in your Webdam account. Each record from your Nexset will be sent as a separate API request to create a resource. The request body should contain the resource data in the format required by the Webdam API, including all required properties for resource creation.

The resource structure must match the Webdam API's expected format. Ensure your resource data includes all required fields. For detailed information about resource creation, request body formats, and available resource properties, see the Webdam API documentation.

Manual configuration

Webdam destinations can also be manually configured to send data to any valid Webdam 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.

Webdam APIs typically expect JSON format for most operations. Endpoint URLs for create operations typically follow the pattern https://apiv2.webdamdb.com/{resource_type}. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

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 Webdam endpoint, open the destination resource menu, and select Activate.

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