Skip to main content
A watchlist is a named set of assets tied to your account. Group the assets you actually care about once, then reuse that grouping to drive dashboards, alerts, portfolio views, or any client that needs a stable list of assets rather than an ad hoc query. Watchlists are the read/write exception in an otherwise read-only surface. Everything else on the Blockworks API answers questions about the market; these endpoints let you create, update, and delete state that belongs to your account.

​
Base URL and authentication

Watchlist endpoints live under /user-management/v1 on the shared Blockworks API host:
Every request requires an API key in the X-Blockworks-API-Key header. See Authentication for details and for where to get a key.
Responses use the standard envelope:

​
Shape of a watchlist

Each watchlist carries an id, a title, the assetIds it contains, and createdAt / updatedAt timestamps. Assets are referenced by UUID, not by slug or symbol, so resolve the identifiers you need from Asset Entities before writing.

​
Two ways to change assets

There are two write paths for the asset list, and picking the wrong one is the easiest mistake to make:
  • Update Watchlist replaces the whole assetIds array when you send one. Omit the field to leave assets untouched; send an empty array to clear them.
  • Update Watchlist Assets adds or removes specific assets and leaves the rest of the list alone.

​
Use cases

  • Track a portfolio or mandate as a named list instead of hardcoding asset IDs in your client.
  • Let your users build their own asset groupings and sync them across your surfaces.
  • Organize assets by sector, theme, or coverage responsibility, then scope reports to a list.
  • Keep a stable set of assets to poll on a schedule as coverage changes.