Brandfolder API
Brandfolder offers a public REST JSON API at developers.brandfolder.com with an OpenAPI reference. Access is self-serve: an API key comes from the user profile page. It covers CRUD on assets, attachments, custom fields, collections, tags, and webhooks, with Python and PHP SDKs.
Frequently asked questions
Brandfolder scores A on the API Report Card. Brandfolder offers a public REST JSON API at developers.brandfolder.com with an OpenAPI reference. Access is self-serve: an API key comes from the user profile page. It covers CRUD on assets, attachments, custom fields, collections, tags, and webhooks, with Python and PHP SDKs.
Brandfolder has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Brandfolder is a cloud-based Digital Asset Management (DAM) and brand management platform that centralizes brand and marketing assets, images, video, logos, documents, templates, for distribution across marketing, sales, creative, and partner channels.
Brandfolder is horizontal/cross-industry and is sold into mid-market and enterprise marketing, brand, and creative organizations. Centralized brand asset library with role-based permissions and external share links. AI-powered auto-tagging, visual similarity search, and duplicate detection ("Brand Intelligence").
Medium. Brandfolder is consistently named in G2's Enterprise DAM grid alongside Bynder, Canto, Acquia DAM (Widen), and MediaValet, and is one of the top DAM brands by G2 Popularity in 2026.
Founded: 2012, Denver, CO. Acquired: by Smartsheet, September 2020, for $155M. Parent: Smartsheet Inc. (NYSE: SMAR, taken private 2025). Notable customers: Lyft, Kroger, Anheuser-Busch, P.F. Chang's, Russell Stover, Slack.
Founded in 2012 in Denver, CO; acquired by Smartsheet in September 2020 for $155M. The product is cloud-native with AI features (Brand Intelligence, similarity search), a public REST API, OAuth-style API keys, webhooks, and modern SDKs.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.