Skip to main content
Convertly HDAM stores library metadata on each file: tags, description, dedicated alt text and captions, rights information, and workspace-defined custom metadata. Metadata powers dashboard search, public faceted search APIs, and CDN delivery identifiers (file id and slug).

Metadata fields

Custom metadata, rights, and alt text

Custom metadata in Convertly is the Custom metadata section of the asset Metadata tab. Define reusable workspace fields such as campaign ID, photographer, product SKU, approval status, or publishing date, choose a field type, and then assign values independently on each asset. Supported field types are text, long_text, number, date, boolean, url, single_select, and multi_select. Values are validated against their workspace field definition. Dedicated alt text, captions, and rights fields are kept separate from custom fields so accessibility and licensing information retain consistent semantics across integrations. Retrieve the full asset record with a files:read API key:
The response contains:
  • governance: alt-text treatment, alt text, caption, rights, and custom field values
  • fields: the workspace custom-metadata definitions needed to interpret customFields
  • usage: 30-day and tracked-lifetime origin requests and generated bytes
  • collections: available collections and whether this asset belongs to each one
  • relationships: source, derivative, variant, companion, and related-asset links
Update values with a files:write key:
Create a reusable custom field through the same endpoint:

Asset usage and relationships API

Asset usage is returned by GET /api/files/{id}/asset-details. Convertly stores daily aggregates rather than visitor-level request logs. Per-asset figures count requests that reached Convertly processing and generated response bytes; browser and edge-cache hits are not attributed to an individual asset. Create a relationship after finding the target with GET /api/files/search?q=...:
Remove it by sending {"action":"remove_relationship","relationshipId":"..."}. Relationship targets are checked against the same workspace; cross-workspace links are rejected by both the API and database policy. Update metadata with PATCH /api/files/{id} or the SDK:
Tags submitted through the API are normalized against your workspace taxonomy when present (synonyms resolve to canonical labels).

AI auto-tagging (SDK one-liner)

Generate searchable tags with Forma AI and persist them on the file in one call:
REST equivalent:
Auto-tagging is available for images up to 25 MB and consumes Forma AI quota. Supported image tags are embedded back into the file when the format allows.
POST /api/files/{id}/auto-tags remains available for dashboard compatibility. Prefer /ai-tags for new integrations.
Search the main workspace library with combined text query, tag filters, orientation, mime type, and optional facet counts — for example sunset + vertical + editorial:
REST:
Faceted search applies to the main workspace library (not WordPress isolated buckets). Isolated site tokens should use GET /api/files with q for scoped listing.

Taxonomy, synonyms, and locales

Define a controlled vocabulary per workspace and locale. Synonyms map contributor input ("portrait") to canonical slugs (portrait-orientation) used in search filters.
Each term is scoped to a workspace and locale. Duplicate slugs per locale return 409. AI auto-tagging and manual tag updates canonicalize against the active locale taxonomy when available.

Contributor tag UI (dashboard)

Contributors do not need a separate tagging product — the dashboard already exposes metadata editing in the Assets lightbox:
  1. Open any file in Assets and expand the info sidebar.
  2. Edit Tags inline (type and press Enter, or remove with the chip control).
  3. Use Auto tags on images to run the same AI pipeline as convertly.ai.tagFile, then review and save.
The lightbox uses the same PATCH /api/files/{id} metadata path as the API. Taxonomy canonicalization applies on save when terms exist for the workspace locale. For stock or contributor portals you build on top of Convertly, wire your UI to:
  • convertly.storage.files.update(id, { tags }) for manual tagging
  • convertly.ai.tagFile(id) for AI suggestions
  • convertly.storage.files.search({ tags, tagMode: "all" }) for public browse pages

Files and storage

Uploads, folders, CDN slugs, and storage limits.

JavaScript SDK

convertly.ai, convertly.storage.files.search, and taxonomy helpers.
Last modified on July 31, 2026