Webdam REST API

Name: Webdam REST API API
Brand: Webdam REST API
Availability: InStock

✓ Official Vendor SpecMediaContent Deliveryoauth220 EndpointsREST

For Agents

Manage Webdam digital assets, folders, lightboxes, and search programmatically for brand-controlled creative distribution.

Quickstart

Get started with Webdam REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search the Webdam asset library"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Webdam REST API API.

Obtain an OAuth 2.0 access token via POST /oauth2/token to authenticate subsequent calls

Browse the folder tree, including subfolders and assets within each folder

Upload an approved asset into a target folder with POST /folders/{folderId}/assets

Update asset metadata or delete an expired asset by assetId

GET STARTED

Start building with Webdam REST API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Webdam REST API API for, with concrete tasks.

★ Approved Creative Distribution

Brand teams that need to push freshly approved creative into channel partner workflows automate the upload and link-sharing path. The agent obtains an OAuth token, calls POST /folders/{folderId}/assets to upload the file, and then calls GET /assets/{assetId}/download to surface a download URL that can be shared with the partner without exposing the dashboard.

POST a logo file to /folders/12345/assets and return the resulting asset's /download URL.

Campaign Lightbox Curation

Marketing managers running a multi-asset campaign use lightboxes to group approved creative for a specific launch. The agent calls POST /lightboxes to create the lightbox, runs GET /search for the campaign keyword, and POSTs each matching assetId to /lightboxes/{lightboxId}/assets so the campaign team has a single ready-to-share collection.

POST /lightboxes with name 'Q4 Launch', then for each asset returned by GET /search?q='Q4 launch' POST it to /lightboxes/{lightboxId}/assets.

Folder Tree Audit and Cleanup

Operations teams that own asset hygiene walk the folder hierarchy via GET /folders/{folderId}/folders and GET /folders/{folderId}/assets, identify assets that have aged out or duplicate the same name in multiple folders, and call DELETE /assets/{assetId} or DELETE /folders/{folderId} to clean up. This makes governance of a multi-thousand-asset library practical.

Recursively walk /folders/{folderId}/folders, list assets per folder, and DELETE assets whose updated_at is older than 24 months.

Agent-Assisted Asset Search

An AI agent helping a marketer find on-brand imagery for a deck calls GET /search with the prompt's keywords, ranks results by metadata match, and returns download URLs through GET /assets/{assetId}/download. The OAuth token is held in Jentic so the agent never sees the raw client secret, which matters for tightly governed asset libraries.

Call GET /search?q='blue product shot landscape' and return the top 5 download URLs from /assets/{assetId}/download.

Key Endpoints

20 endpoints — webdam (now part of bynder) is a digital asset management platform used by marketing and brand teams to organise and distribute approved creative.

METHOD

PATH

DESCRIPTION

POST

/oauth2/token

Obtain an access token

GET

/assets/{assetId}

Get asset details

GET

/assets/{assetId}/download

Download an asset

POST

/folders/{folderId}/assets

Upload asset to folder

GET

/search

Search assets

POST

/lightboxes

Create a lightbox

POST

/lightboxes/{lightboxId}/assets

Add an asset to a lightbox

DELETE

/assets/{assetId}

Delete an asset

POST

/oauth2/token

Obtain an access token

GET

/assets/{assetId}

Get asset details

GET

/assets/{assetId}/download

Download an asset

POST

/folders/{folderId}/assets

Upload asset to folder

GET

/search

Search assets

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Webdam OAuth client credentials and issued access tokens are stored encrypted in the Jentic vault. Agents receive a scoped runtime credential when they call /assets, /folders, /lightboxes, or /search, so the raw client secret never lands in prompts or logs.

Intent-based discovery

Agents search Jentic for 'upload an asset to Webdam' or 'search the Webdam library' and Jentic returns the matching operation with its input schema, so the agent can call POST /folders/{folderId}/assets or GET /search directly without reading the developer documentation.

Time to first call

Direct Webdam integration: 1-2 days to handle the OAuth flow, folder tree walk, and binary upload pattern. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Brandfolder API

DAM platform with similar asset, folder, and search surface aimed at brand teams.

Choose Brandfolder when the team is already a Brandfolder customer; choose Webdam when the parent Bynder ecosystem is in use.

Alternative

Cloudinary Admin API

Developer-focused image and video DAM with strong transformation pipeline.

Choose Cloudinary when the workflow is engineering-led with on-the-fly transformation; choose Webdam when brand governance and approval workflows matter most.

Complementary

Dropbox API v2

General-purpose file storage that can stage assets before they land in Webdam.

Use Dropbox as the working storage for in-flight creative, then promote approved assets into Webdam via POST /folders/{folderId}/assets.

Complementary

Box Content API

Enterprise content storage that pairs with Webdam as a wider document store.

Keep general business documents in Box and elevate creative-only assets into Webdam where brand governance applies.

FAQs

Specific to using Webdam REST API API through Jentic.

What authentication does the Webdam REST API use?

Webdam uses OAuth 2.0. You call POST /oauth2/token with your client credentials to obtain an access token, then pass it as Authorization: Bearer <token> on every subsequent request to apiv2.webdamdb.com. Through Jentic the OAuth client credentials are stored encrypted in the vault and the agent receives a scoped runtime token, so the raw client secret is never exposed.

Can I upload an asset into a Webdam folder via the API?

Yes. POST /folders/{folderId}/assets accepts the binary upload along with metadata such as filename and description. Use GET /folders/{folderId}/folders to walk the tree to the right destination folder before uploading.

What are the rate limits for the Webdam REST API?

The OpenAPI spec does not declare hard rate limits. Webdam's published guidance is plan-dependent; for sustained automation, treat 5 requests per second per token as a safe ceiling and stagger bulk uploads by chunking work across multiple short batches.

How do I download a Webdam asset through Jentic?

Install pip install jentic and run an agent with the search query 'download a Webdam asset'. Jentic returns the GET /assets/{assetId}/download operation with its input schema; the agent supplies the assetId and writes the response binary to disk or to a downstream storage system.

Can I search the Webdam library by keyword?

Yes. GET /search accepts a query parameter and returns matching asset records. Pair it with POST /lightboxes and POST /lightboxes/{lightboxId}/assets to convert a search result list into a curated collection for a campaign.

Is the Webdam REST API free?

API access is included with paid Webdam (now Bynder) plans; there is no free tier for the platform itself. The API does not impose a per-call charge, so the constraint is the underlying plan rather than per-request pricing.