Skip to content
Dark mode

Asset Hub

Discover hubs and assets, manage hub access, create and organize assets, and maintain the attribute taxonomy in Asset Hub.

The Asset Hub APIs let you discover and retrieve content from your organization’s Asset Hubs, and automate the lifecycle of that content. Use them to list active hubs and published assets, to read metadata, media files, and transcripts, and to create hubs, manage collaborators and user access, process assets in bulk, and maintain your attribute taxonomy.

  • Hub and asset discovery: Retrieve paginated lists of all active hubs and the published assets they contain.
  • Asset details: Access metadata and attributes for specific assets so they display accurately in third-party applications.
  • Media and transcript retrieval: Fetch signed URLs for raw content files, along with thumbnails and text transcripts.
  • Hub management: Create restricted or public hubs to scale your content organization.
  • Access control: Bulk update hub collaborator permissions and control individual user access to restricted hubs.
  • Asset operations: Create assets asynchronously, delete them permanently, move or mirror them across hubs, and archive them in bulk.
  • Taxonomy governance: Create attribute categories, create attributes within them, and delete attributes when they are no longer needed.

To call these endpoints, you need to be familiar with the following platform standards:

  • Authentication: How to generate and use your Bearer token.
  • Base URLs: The correct regional endpoint for your account.
  • Rate limits: Platform quotas and retry logic.
  • Conventions: Standard JSON data formats and HTTP status codes.

For more information, see Authentication and setup.

The content discovery endpoints, List active hubs and List published assets in a hub, support pagination with limit and skip. Async status endpoints document their own pagination defaults.

  • limit: Maximum number of results per page. Default is 100. Maximum allowed is 100.
  • skip: Number of results to skip.

Example:

{
"limit": 100,
"skip": 200
}

You can filter assets and hubs with these fields:

  • hub_ids: array of strings.
  • asset_ids: array of strings.
  • sharing_type: EXTERNAL or INTERNAL.

Invalid IDs are silently ignored, and the response omits non-matching results.

Use order_by to sort list responses. Both field and order are required.

  • field: title, created_at, updated_at, and the other columns each list endpoint supports.
  • order: ASC or DESC.

Example:

{
"order_by": {
"field": "created_at",
"order": "ASC"
}
}