Skip to main content
​
2026.02.02

​
Transaction status reason code update

SummaryAdded a new transaction status reason code provider-maximum-limit-exceeded to provide more specific error information when a transaction fails due to provider-imposed maximum limits. This replaces the previous amount-limit-exceeded reason code for failed transactions.This change improves error clarity by distinguishing provider-specific maximum limit errors from other amount limit scenarios.DocumentationAction required
  • ⚠️ Breaking Change: Update your integrations to check for provider-maximum-limit-exceeded instead of amount-limit-exceeded in the statusDetails.reason field of failed transactions.
  • ❌ The amount-limit-exceeded reason code will no longer be returned.
​
2026.01.26

​
Metadata support in the API

SummaryIntroduced new endpoints to manage metadata for API resources. Partners can now programmatically create, update, retrieve, and delete custom metadata for supported entities, enabling more flexible integrations and resource annotations.This feature allows you to attach arbitrary key-value data to resources, such as accounts or users, to support custom workflows, tagging, or additional business logic.Documentation
​
2026.01.26

​
Travel Rule compliance for crypto transactions

SummaryAdded Travel Rule compliance for crypto deposits (handled by RFIs) and crypto withdrawals (handled by quote requirements), along with an embeddable Travel Rule widget to collect the required originator and beneficiary information.Details
  • Transaction RFIs: New endpoints to get, list, and update requests for information (RFIs) for crypto deposits that require Travel Rule data.
  • Quote Requirements: Quotes now return travel-rule requirements when additional information is needed before executing crypto withdrawals.
  • Travel Rule Widget: Embeddable widget for collecting originator and beneficiary information.
DocumentationActions required
  • 🔔 Monitor core.transaction.status-changed webhooks for transactions with status on-hold
  • 🔍 Check for travel-rule requirements in quote responses when creating crypto withdrawal quotes
  • 🚀 Integrate the Travel Rule widget to handle compliant data collection for affected transactions
​
2026.01.26

​
Validate network address endpoint

SummaryIntroduced a new endpoint to programmatically validate the format of a network address before initiating a transaction. This helps ensure only valid crypto addresses are used, reducing the risk of user errors and failed transfers. Currently, validation is supported for addresses on crypto networks.Documentation
​
2026.01.26

​
Support for multiple address formats in crypto deposit methods

SummaryThe Set Up Account Deposit Method endpoint now supports multiple crypto address formats for a single deposit method. Partners can now retrieve and display all supported address formats (e.g., native-segwit, wrapped-segwit, pubkey-hash) for a given network and asset, improving user experience and compatibility.Documentation
​
2026.01.12

​
New public Postman workspace

SummaryWe’ve launched a new public Postman Workspace to reduce friction when accessing our API collections, enabling a smoother developer-experience.The previous invite-only workspace will remain accessible until 25th of January 2026, but it won’t receive further updates.Actions required
  • Follow the updated Quick Start guide to set up the new Postman workspace. While the setup process is largely unchanged, environment variables have been renamed for clarity.
Documentation
​
2025.12.05

​
Skip assets cooldowns test helper

SummaryIntroduced a new Test Helper endpoint to instantly bypass asset cooldowns in Sandbox environments.Asset cooldowns temporarily restrict features like buy and deposit for compliance reasons. This test helper allows you to skip the waiting period during development and testing, enabling immediate access to all asset features.For example, when testing with GB users, you can bypass the 24-hour cooldown and immediately test deposit or purchase flows.Documentation
​
2025.12.03

​
Business users

SummaryThe API has been expanded to support business users, enabling interactions similar to those available for individual users.At this stage, business users must be created and KYB’ed outside the API. Reach out to your Account Manager if you have a use-case where business users are needed.Once verified, a business user can be managed through the API, including creating accounts, linking external accounts, and initiating transactions.DocumentationThe documentation now includes badges to indicate the supported subject types for each endpoint.
​
2025.11.26

​
Terms of Service update for EEA users

SummaryAdded 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.DocumentationActions 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

SummaryEnhanced 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
DocumentationActions 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

SummaryExpanded 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.
DocumentationActions 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

SummaryIntroduced 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.DocumentationActions 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

SummaryIntroduced 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

SummaryIntroduced 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

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

​
Asset ordering

SummaryIntroduced 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

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

​
Asset cooldowns

SummaryEnhanced 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

SummaryIntroduced the Core API, providing the foundational infrastructure for building financial applications on Uphold.Included featuresThis 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