The Brand API Register
File management (DAM)

Bynder API

Bynder's REST API and MCP server reach a company's approved assets in its portal, with its permission, and its brand guides with the CX User Community package.

Last updated 2026-11-10

Bynder is a digital asset management (DAM) system. A company keeps its approved images, documents and video there, with metadata and the rights that say who may download what. The REST API, on the company's own portal domain with OAuth 2.0, searches and downloads those assets. Brand guidelines live in a separate package, CX User Community, whose API returns guide pages as structured widgets. Bynder MCP lets agents search and read the same material.

It suits products whose customers keep their approved files in Bynder.

  • Logos Partly
  • Colours Partly
  • Fonts Partly
  • Guidance Yes
  • Files Yes

What does Bynder return?

  • LogosNo logo-specific endpoint; the asset types are image, document, audio, video and 3d, so logos come back as ordinary assets.
  • ColoursOnly through CX User Community guides: a colour widget on a guide page lists named colours with their codes (hex, RGB, CMYK).
  • FontsNo font endpoint; the MCP answers questions about fonts from published CX User Community content.
  • GuidanceThe CX User Community API returns guides, groups and pages, with each page's widgets (text, title, colour, image, table and others) as JSON.
  • FilesReturns the portal's assets of type image, document, audio, video and 3d, with their metadata; the download endpoint gives a temporary URL for the original or additional files.

How is it billed?

Modular plans customized per customer around the core DAM, with modules such as AI search, CX User Community and workflow.

What are the limits?

4,500 requests per five-minute window from a single IP address; above that, HTTP 429 and a five-minute cooldown.

What do the terms require?

Downloading an asset needs the MEDIAHIGHRES role, plus extra roles for archived, watermarked or limited-usage assets.

Who keeps it current?

The customer's team, which maintains assets and guides in its portal; MCP answers use the current published version of each guide.

How do you call it?

curl -X POST "https://{portal-domain}.bynder.com/v6/authentication/oauth2/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "grant_type=client_credentials" \
  --data-urlencode "client_id={client_id}" \
  --data-urlencode "client_secret={client_secret}" \
  --data-urlencode "scope={scope}"

When should you use something else?

  • For logos and colours as data, Bynder has no logo or colour endpoint. Logos are ordinary assets, and colours exist only as widgets on guide pages.
  • For guidelines through MCP, the customer needs the CX User Community package; without it, Bynder MCP searches assets only.
  • For agents making new work, see agentic brand work. Bynder MCP searches and reads; choosing what fits a task is left to the agent.

Sources