Skip to main content
2025.11.26

Terms of Service update for EEA users

Summary
Added general-pt-bop as a new Terms of Service code for EEA users, available starting December 10, 2025 at 10:00 AM UTC. The existing general-lt-fcs code remains accepted through the end of 2025.
DocumentationAction Required
  • Use general-pt-bop for new EEA users starting December 10, 2025 at 10:00 AM UTC.
  • Display updated Terms of Service to existing EEA users (previous acceptances automatically migrated).
2025.11.25

EU and UK Tax Reporting Regulatory Requirements

Summary
Enhanced KYC processes to support EU and UK tax reporting regulatory requirements. The profile and taxDetails processes now dynamically adapt to the user’s country, collecting additional required properties for compliance.
Enforcement Dates
  • EU users: Starting on December 10, 2025 at 10:00 AM UTC for all users.
  • UK users: Starting on December 30, 2025 at 10:00 AM UTC for newly registered users.
Details
  • Profile: Collects place of birth and other citizenships for EU users
  • Tax Details: Supports tax address and multiple tax residence countries with flexible data collection when tax IDs cannot be provided
  • Dynamic Forms: Uses JSON Forms with progressive disclosure based on user responses
DocumentationAction Required
  • ⚠️ Breaking Change: profile object structure has changed in Get KYC Overview and Update Profile endpoints:
    • Properties moved to input.details (previously input).
    • The citizenshipCountry has been renamed to primaryCitizenship.
    • New profile.hint object with dynamic schema and uiSchema.
    • The legacy static structure is deprecated but still supported for backward compatibility. See Update Profile for both versions.
    • Update response parsing and property names in your integration.
  • 🔍 Check taxDetails.status and use taxDetails.hint.schema to collect required properties.
2025.10.08

Crypto Deposits and Withdrawals

This feature is currently available only in the Sandbox environment.
Summary
Expanded support for crypto funding flows, enabling seamless deposits and withdrawals in crypto.
Details
  • New Capabilities: Introduced bank-deposits and crypto-deposits. The existing deposits capability remains available for other deposit types.
  • Networks: Added network.type to List Networks as a validation hint for frontend integrations.
  • Quotes / Transactions: The crypto-address node now includes an execution object supporting three modes — onchain, offchain, and simulated. Learn more about it here.
  • CDD for US Users: All users (including US users) will require to Update customer due diligence before making a crypto deposit or crypto withdrawal.
DocumentationAction Required
  • ⚠️ Update your integrations to read destination.node.execution.transactionHash instead of destination.node.transactionHash.
  • ❌ The old property will no longer return a value.
  • 🔔 Ensure your app handles Customer Due Diligence for all users (including US users) before enabling crypto deposits or withdrawals.
2025.09.29

Assets Cooldown Ended Webhook

Summary
Introduced a new webhook that notifies platforms when a user’s asset cooldown period ends. This enables partners to update asset availability, unlock trading actions, and notify users in real-time, without relying on polling.
DocumentationAction Required
  • ✅ No changes needed if cooldown tracking is not required for your use case.
  • 🔔 Subscribe to this webhook to refresh asset states and proactively notify users when cooldowns end.
2025.09.12

Topper API

Summary
Introduced the Topper API to enable KYC sharing between partners and the Topper Widget, allowing partners to complete the KYC of a Topper user directly via the Core API.
Documentation
2025.09.03

Portfolio Endpoints

Summary
Introduced a group of endpoints to provide aggregated insights into a user’s financial position across all accounts.
Documentation
2025.08.08

FPS Deposits and Withdrawals

Summary
Introduced support for deposits and withdrawals via the Faster Payments System (FPS).
Documentation
2025.07.01

Asset Ordering

Summary
Introduced support for sorting assets by various criteria, including market cap, price, and price variance. This enhancement enables partners to retrieve ordered asset lists from the API, eliminating the need for custom sorting logic.
Documentation
2025.05.06

Widgets API

Summary
Introduced the Widgets API, enabling partners to create secure sessions for embedding Uphold widgets in their applications.
Documentation
2025.05.06

Asset Cooldowns

Summary
Enhanced the Assets schema by introducing a cooldowns property to provide details about any active cooldowns applied to the asset. This allows partners to understand which assets are temporarily restricted and when they become available again.
Documentation
2025.04.23

Core API

Summary
Introduced the Core API, providing the foundational infrastructure for building financial applications on Uphold.
Included Features
This initial release introduced all foundational components of the Core API, including:
  • Authentication Endpoint to request access tokens using the OAuth2 protocol.
  • Countries Endpoints to retrieve information about the supported countries.
  • Users Endpoints to manage users, providing full CRUD capabilities and real-time webhooks to stay informed about user changes.
  • KYC Endpoints to manage KYC processes, ensuring that users are compliant with regulatory requirements. It also includes webhooks to notify about KYC status changes in real time.
  • Capabilities Endpoints to retrieve capabilities, the actions and features that users can perform on the platform.
  • Terms of Service Endpoints to retrieve applicable Terms of Service and record user acceptance, ensuring compliance with legal requirements.
  • Files Endpoints to generate upload and download links that support file-based KYC processes.
  • Assets Endpoints to retrieve information about the assets available on the platform, as well as the networks and rails used to transfer them.
  • Accounts Endpoints to manage users’ accounts, along with webhooks to asynchronously notify about account changes and balance updates.
  • External Accounts Endpoints to link and manage financial accounts that users own outside the platform, such as debit or credit cards, enabling both pull deposits (moving funds into Uphold) and withdrawals (sending funds out of Uphold).
  • Transactions Endpoints to initiate and retrieve transactions through a unified RFQ (Request for Quote) model, supporting deposits, withdrawals, trades, and transfers across multiple asset types, along with webhooks to notify about transaction changes.
Documentation