Install Jentic One Beta

Connect the Webdam REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webdam REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdamsuccess.com%2Fdamsuccess" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdamsuccess.com%2Fdamsuccess" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Webdam REST 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

Download a Webdam asset binary via GET /assets/{assetId}/download for distribution

GET STARTED

Start building with Webdam REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Webdam REST 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

/lightboxes

Create a lightbox

POST

/lightboxes/{lightboxId}/assets

Add an asset to a lightbox

DELETE

/assets/{assetId}

Delete an asset

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Webdam by hand means implementing its OAuth2 token flow against apiv2.webdamdb.com and building the upload, search, and retry plumbing for assets and lightboxes yourself. Through Jentic you install once, import the Webdam REST API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Webdam puts the asset and folder ids in the URL path (/assets/{assetId}, /folders/{folderId}/assets), so a rule can pin your agent to one folder for adding assets and to specific assets for reads and downloads. You choose the operations it may call, so deleting an asset is not included unless you add it.

Credential isolation

Your Webdam OAuth client credentials and issued access tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload an asset to Webdam' or 'search the Webdam library', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the developer documentation.

FAQs

Specific to using Webdam REST 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.

Can I limit what my agent is allowed to do with the Webdam REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Webdam operations and credentials the agent may use. Webdam carries the asset and folder ids in the URL path (/assets/{assetId}, /folders/{folderId}/assets), so you can pin the agent to a single folder for uploads and to specific assets for reads and downloads via GET /assets/{assetId}/download. You choose the operations it can call, so DELETE /assets/{assetId} stays off the list unless you explicitly allow it.

Damsuccess Webdam REST API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaContent Deliveryoauth220 EndpointsREST

For Agents

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

Use for: I need to upload a new approved asset into a Webdam folder, Search Webdam for assets matching a campaign keyword, Download a specific Webdam asset by ID, Create a lightbox for a campaign and add assets to it

Not supported: Does not handle CDN delivery configuration, image transformations, or licence rights tracking - use for Webdam asset, folder, lightbox, and search management only.

Webdam (now part of Bynder) is a digital asset management platform used by marketing and brand teams to organise and distribute approved creative. The REST API exposes 20 endpoints covering OAuth token issuance, asset upload and retrieval, folder hierarchy management, lightboxes for curated collections, search, and user lookup. It targets enterprise teams that need programmatic access to a controlled asset library rather than a general-purpose file store.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

30%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Webdam REST API to your agent

Capabilities

Start building with Webdam REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Damsuccess Webdam REST API

Jentic AI Readiness Score

Webdam REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness