Skip to main content

Overview

The Assets API is the catalog for assets available through Payward Services. Use it before a payment or trading flow to decide which assets to show, how much precision to accept, and whether deposits, withdrawals, or swaps are currently enabled. The same responses also include display metadata and market data. Use this data to build asset pickers, payment setup screens, and price history views.

Prerequisites

  • Payward Services API credentials (see the Authentication guide)
  • Base URL: https://api.services.payward.com

Asset discovery workflow

Use this flow when you build a screen that lets a user choose an asset, review its details, and continue into a deposit, withdrawal, or trade.
1

List available assets

Filter the catalog to assets enabled for the action you want to offer.GET /v1/assets
2

Inspect the selected asset

Fetch the asset again when the user selects it. Check current status, precision, logo, and quote-denominated market data.GET /v1/assets/{asset_type}/{asset_symbol}
3

Show price history

Fetch historical rates when you need a chart, recent trend, or change-over-time display.GET /v1/assets/{asset_type}/{asset_symbol}/rates
4

Continue to the user action

Use the selected symbol with the deposits, withdrawals, or trade endpoints.See Deposits and withdrawals.
Asset prices and rates are useful for display and discovery. Do not use them as executable trade quotes. Use the Swap API when you need a locked trading price.

Step 1: list available assets

Call GET /v1/assets to build the asset list for your UI. Filter by asset type and capability so users only see assets that support the action they are trying to complete.
Use these fields from each asset: The list endpoint is cursor-paginated. If the response includes next_page_token, pass it as page_token to fetch the next page. See the List Assets API reference for all filters, sort options, and response fields.

Step 2: inspect the selected asset

Call GET /v1/assets/{asset_type}/{asset_symbol} when the user selects an asset. This gives you the same normalized shape as the list response, scoped to one asset.
Before you continue:
  • Check status.deposit.enabled before you create or show deposit addresses.
  • Check status.withdraw.enabled before you list withdrawal methods or let a user save a withdrawal address.
  • Use decimals.funding to format and validate payment amounts.
  • Use quote_symbol and quote_type consistently so your UI does not mix valuations from different quote assets.
See the Get Asset API reference for the full response schema.

Step 3: show price history

Call GET /v1/assets/{asset_type}/{asset_symbol}/rates when you need historical prices for a chart or trend display. Set the quote asset, time window, and interval explicitly.
Supported intervals include PT1M, PT5M, PT15M, PT30M, PT60M, PT4H, P1D, P7D, and P15D. Use the next_page_token from the response when you need more history. See the List Asset Rates API reference for all query parameters and pagination behavior.

User-scoped asset views

Each endpoint above has a user-scoped variant under /v1/users/{user_id}/assets. These return the same asset shape, scoped to one user — reflecting that user’s eligibility and any per-account restrictions on deposit, withdrawal, or trading. Use the public endpoints to build a general catalog. Use the user-scoped variants when you already know which user the screen is for and want availability that matches that specific account. Pass the user’s IIBAN as user_id:
  • GET /v1/users/{user_id}/assets
  • GET /v1/users/{user_id}/assets/{asset_type}/{asset_symbol}
  • GET /v1/users/{user_id}/assets/{asset_type}/{asset_symbol}/rates
Query parameters, pagination, and response fields match their public counterparts.

API reference