Brandfolder OpenAPI Reference

Name: Brandfolder OpenAPI Reference API
Brand: Brandfolder OpenAPI Reference
Availability: InStock

✓ Official Vendor SpecMediaContent Deliverybearer73 EndpointsREST

For Agents

List, upload, tag, and search digital assets in a Brandfolder DAM through 73 v4 endpoints, with custom fields and collections for organising brand libraries.

Install Jentic One Beta

Connect the Brandfolder OpenAPI Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brandfolder OpenAPI Reference, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Brandfolder OpenAPI Reference API.

List the brandfolders in an organization via GET /brandfolders and drill into one with GET /brandfolders/{brandfolder_id}

Upload new assets into a brandfolder or collection through POST /brandfolders/{brandfolder_id}/assets and POST /collections/{collection_id}/assets

Tag assets in bulk with POST /assets/{asset_id}/tags and rename or delete tags via PUT/DELETE /tags/{tag_id}

GET STARTED

Start building with Brandfolder OpenAPI Reference API

Explore with Jentic

View OpenAPI Document

Brandfolder by Smartsheet is a digital asset management platform whose v4 API exposes 73 endpoints for managing brand assets, attachments, collections, sections, tags, and custom fields. The API is organised around organizations and brandfolders, with assets nested under sections and grouped through collections, and supports both per-asset operations and bulk asset upload. Custom field keys and values let teams attach arbitrary metadata to assets so creative, marketing, and product teams can search and filter the brand library by their own taxonomy. Authentication is a bearer API token scoped to the user's organization.

Use Cases

Patterns agents use Brandfolder OpenAPI Reference API for, with concrete tasks.

★ Centralised brand asset upload pipeline

Push approved creative from a design tool or CI step into Brandfolder so a single source of truth exists for logos, product images, and marketing collateral. The pipeline calls POST /brandfolders/{brandfolder_id}/assets with the file and metadata, optionally placing the asset in a section, and Brandfolder returns the asset id and attachment record. This removes ad-hoc Dropbox and email handoff and keeps the canonical brand library current.

POST /brandfolders/{brandfolder_id}/assets with name 'spring-campaign-hero', a base64 attachment, and section_id, then return the asset.id from the response.

Tag-driven asset search for marketing teams

Marketing teams need to retrieve every asset tied to a campaign or product without scrolling the UI. Apply tags through POST /assets/{asset_id}/tags at upload time, then list and filter assets with GET /brandfolders/{brandfolder_id}/assets to surface a campaign's hero images, social cuts, and PDFs in one call. Tag rename and delete operations keep the taxonomy clean as campaigns retire.

GET /brandfolders/{brandfolder_id}/assets with a tag query for 'spring-2026' and return the list of asset.attributes.name and asset.attributes.thumbnail_url.

Custom-field metadata for licence and rights tracking

Legal and brand teams need to know which assets are licensed, when the licence expires, and which markets each asset can run in. Define custom field keys with POST /brandfolders/{brandfolder_id}/custom_field_keys, then write per-asset values via POST /custom_field_keys/{custom_field_key_id}/custom_field_values. Searches and exports can then filter by licence_expiry or usage_rights without bolting on a separate metadata system.

Create a custom_field_key 'licence_expiry' on a brandfolder, then write the value '2026-12-31' against asset {asset_id} via POST /custom_field_keys/{key_id}/custom_field_values.

Collection roll-ups for product launches

Pull all assets needed for a specific launch — product photography, hero banners, video stills, datasheets — into a single collection so external agencies and channel partners can be granted scoped access. Create the collection with POST /brandfolders/{brandfolder_id}/collections, then attach assets via POST /collections/{collection_id}/assets. This replaces ad-hoc shared drives for each launch.

POST /brandfolders/{brandfolder_id}/collections with name 'Q3 Launch', then for each provided asset_id call POST /collections/{collection_id}/assets to add it.

AI agent integration via Jentic

An agent producing campaign content needs to drop final renders into Brandfolder without holding a long-lived API token. Through Jentic, the agent searches by intent, loads the upload-asset operation, and executes it; the bearer token stays in the Jentic vault and the agent only handles file content and metadata.

Through Jentic, search 'upload a brand asset to a digital asset library', load the create-asset operation, and execute with brandfolder_id, name, and the asset file.

Key Endpoints

73 endpoints — brandfolder by smartsheet is a digital asset management platform whose v4 api exposes 73 endpoints for managing brand assets, attachments, collections, sections, tags, and custom fields.

METHOD

PATH

DESCRIPTION

GET

/brandfolders

List the brandfolders the API token can access

POST

/brandfolders/{brandfolder_id}/assets

Upload a new asset into a brandfolder

GET

/brandfolders/{brandfolder_id}/assets

List or search assets in a brandfolder

GET

/assets/{asset_id}

Retrieve a single asset and its metadata

POST

/assets/{asset_id}/tags

Tag an asset with one or more labels

POST

/brandfolders/{brandfolder_id}/collections

Create a collection inside a brandfolder

POST

/brandfolders/{brandfolder_id}/custom_field_keys

Define a custom field key for a brandfolder

GET

/brandfolders

List the brandfolders the API token can access

POST

/brandfolders/{brandfolder_id}/assets

Upload a new asset into a brandfolder

GET

/brandfolders/{brandfolder_id}/assets

List or search assets in a brandfolder

GET

/assets/{asset_id}

Retrieve a single asset and its metadata

POST

/assets/{asset_id}/tags

Tag an asset with one or more labels

Why Jentic?

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

Credential isolation

Brandfolder bearer API tokens are stored encrypted in the Jentic vault and attached to the Authorization header on every /api/v4 request at execution time. Agents call asset operations by intent; raw tokens never enter prompts, traces, or logs.

Intent-based discovery

Agents search Jentic for intents like 'upload a brand asset' or 'tag an asset' and Jentic returns the matching Brandfolder operation (POST /brandfolders/{brandfolder_id}/assets, POST /assets/{asset_id}/tags) with input schemas already typed.

Time to first call

Direct Brandfolder integration: 1-3 days to handle multipart upload, custom field shaping, and pagination across 73 endpoints. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Brandfolder OpenAPI Reference API through Jentic.

What authentication does the Brandfolder API use?

The v4 API uses an HTTP bearer API token attached as Authorization: Bearer {token}. Through Jentic, the token is stored encrypted and injected at request time, so individual asset uploads or tag updates do not need the agent to handle the raw credential.

Can I upload assets to Brandfolder through the API?

Yes. POST /brandfolders/{brandfolder_id}/assets uploads a new asset directly into a brandfolder, and POST /collections/{collection_id}/assets adds an asset to a collection. The response includes the new asset.id and attachment.id you can reference in subsequent calls.

How do I tag assets in Brandfolder via the API?

Call POST /assets/{asset_id}/tags with a list of tag names — Brandfolder creates any that do not exist on the brandfolder. Existing tags can be renamed via PUT /tags/{tag_id} or removed with DELETE /tags/{tag_id} when a campaign retires.

What are the rate limits for the Brandfolder API?

Brandfolder does not publish a fixed rate limit in the v4 OpenAPI spec; quotas are tied to organization plan. For heavy ingest such as bulk asset upload or large tag operations, batch requests and back off when the API returns 429.

How do I add custom metadata to an asset with the Brandfolder API through Jentic?

Install with pip install jentic, search for 'add custom field value to asset', load the operation that targets POST /custom_field_keys/{custom_field_key_id}/custom_field_values, and execute with asset_id and value. Jentic handles the bearer token attachment and parameter validation.

What is the difference between a section and a collection in the Brandfolder API?

Sections are hierarchical buckets inside a brandfolder created with POST /brandfolders/{brandfolder_id}/sections — each asset belongs to exactly one section. Collections, created with POST /brandfolders/{brandfolder_id}/collections, are cross-cutting groupings an asset can join in addition to its section.

Brandfolder OpenAPI Reference

Connect the Brandfolder OpenAPI Reference to your agent

Capabilities

Start building with Brandfolder OpenAPI Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs