The API Report CardAPI Index
Widen

Widen API

Digital Asset Management (DAM) / Brand & Marketing Content Operations · widen.com

Acquia DAM (Widen) exposes a public REST API with OAuth 2.0, webhooks, and an official TypeScript SDK. Docs are fragmented across Apiary v1, v2, and docs.acquia.com. Unlimited API usage is gated to the quote-priced Enterprise plan; Workgroup gets core access.

Last verified: July 2026Marketing & Sales
API GRADE
C+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST API for Acquia DAM with parallel v1 and v2 references on Apiary.
AccessGOODEvery plan includes core REST access with admin-issued tokens; unlimited API usage is an Enterprise feature.
CoverageMIXEDAssets, metadata, collections, products, and workflow are reachable, but some features still require falling back to v1.
AuthGOODOAuth 2.0 authorization code flow plus long-lived admin-issued tokens for server-to-server use.
Docs & DXGOODOfficial TypeScript SDK, Apiary specs for both versions, Postman collections, and a webhooks management API.
StabilityMIXEDRate limits are tier-dependent and not prominently published; webhook retry and replay semantics are lightly documented.
MORE FROM THE REPORT CARD
Supergood: Widen has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Widen scores C+ on the API Report Card. Acquia DAM (Widen) exposes a public REST API with OAuth 2.0, webhooks, and an official TypeScript SDK. Docs are fragmented across Apiary v1, v2, and docs.acquia.com. Unlimited API usage is gated to the quote-priced Enterprise plan; Workgroup gets core access.

Tried to integrate with Widen?
SOURCES
API documentation is fragmented across three surfaces (Apiary v1, Apiary v2, docs.acquia.com), making it hard for integrators to identify the canonical reference docs.acquia.com
Rate limits and throttling policies are not prominently published, bulk migrations and large asset syncs require trial-and-error tuning and observation of response headers community.acquia.com
Workgroup tier gates 'unlimited REST API access' behind the Enterprise plan, meaning serious integration work effectively requires upgrade acquia.com
Two parallel API versions (v1 and v2) coexist; the TS SDK itself uses v2 as primary but falls back to v1 for features not yet in v2, integrators must straddle both github.com
Only one official SDK (TypeScript), no first-party Python, Java, Ruby, PHP, Go or .NET libraries despite enterprise customer base github.com
Webhook retry semantics, signing, and replay protection are lightly documented relative to enterprise expectations docs.acquia.com
OAuth client provisioning is admin-gated in the DAM UI, third-party integrators cannot self-serve a sandbox without a paid tenant widenv2.docs.apiary.io
Customers report API roadmap has slowed since the Acquia acquisition; new endpoints prioritize Acquia DXP integration over independent integrator needs trustradius.com
Asset expiration / rights-management notifications surfaced via API are reported to fire inconsistently, breaking license-compliance automations trustradius.com
Search is inconsistent and unintuitive, users report difficulty finding assets that coworkers can later locate g2.com
Limited customization of dashboards and portals; portals serve a 'very limited type of audience with almost no customization' g2.com
Steady turnover of account reps post-Acquia acquisition; new reps lack product depth and sometimes go silent on open issues trustradius.com
Asset-expiration notifications for rights-restricted content reported as not working, a critical gap for licensed-asset distribution trustradius.com
Support response times have degraded under Acquia ownership relative to pre-acquisition Widen experience g2.com
Pricing is opaque, quote-driven and skewed toward Enterprise tier for unlimited users / advanced security (SSO gated) acquia.com
InDesign templating and video workflow modules are functional but considered immature relative to Aprimo / Bynder trustradius.com
Brand absorption into Acquia DXP has created identity confusion (widen.com 301s to acquia.com); some customers report friction with the rebrand and shifted GTM motion acquia.com