Entities and Portfolios

Coinbase Prime utilizes a multi-entity, multi-portfolio setup to accommodate both simple and sophisticated organizational structures. A Prime account starts with one portfolio under a single entity. Multiple portfolios may be added inside the same entity to suit different trading strategies, user groups, or operational needs. Entities may also be added for other domiciles or under separate legal structures.

API keys are scoped to a portfolio, entity, or organization. Many REST API calls require an Entity ID or a Portfolio ID, so it’s essential to locate these first. To retrieve existing entity and portfolio IDs, call List Portfolios and parse the response for id (portfolio ID) and entity_id.

PortfoliosService portfoliosService = PrimeServiceFactory.createPortfoliosService(client);

ListPortfoliosResponse response = portfoliosService.listPortfolios();

To learn more about this SDK, please visit the Prime Java SDK.

Most endpoints are scoped to the portfolio level, so they require a Portfolio ID. These include placing an order or creating a withdrawal. Examples of endpoints that are scoped to the entity level include listing payment methods, listing assets, and listing users.

Supported Assets

An asset can be any cryptocurrency (e.g., BTC) or fiat currency (e.g., USD) supported by Coinbase Prime. This is different from a product, which is a tradable pair of assets (e.g., BTC-USD). To retrieve a list of supported assets along with important metadata (precision, supported networks, etc.), call List Assets. This endpoint covers all assets at the entity level, so an Entity ID is required.

AssetsService assetsService = PrimeServiceFactory.createAssetsService(client);

ListAssetsRequest request = new ListAssetsRequest.Builder()
    .entityId("ENTITY_ID_HERE")
    .build();

ListAssetsResponse response = assetsService.listAssets(request);

To learn more about this SDK, please visit the Prime Java SDK.

Please note: All requests discussed above require proper authentication. For more information, visit REST API Authentication.