Skip to main content

42 Updates tagged with "v2 API"

View All Tags

  • v2 API: Add optional crypto_tx_hashes filter to the List Transfers endpoint.
  • v2 API: Add the following document types to Identity Documents APIs: AML_DOCUMENTS, FUND_STRUCTURE_CHART, FUND_MANAGER_REGISTRATION, MEMORANDUM_OF_ASSOCIATION, ORGANIZATIONAL_CHART, FOUNDATION_BY_LAWS, APPOINTMENT_OF_GUARDIAN_EVIDENCE, LEGAL_DOMICILE_OF_BENEFICIAL_OWNERS, GOVERNING_BODY_MEMBER_NAMES.

  • v2 API: Add three new optional fields to the customer_due_diligence object of the Identity API (Create Identity and Update Identity).
  • v2 API: Add new ENUM value GOVERNMENT_BENEFITS to the customer_due_diligence object field source_of_funds in the Identity API (Create Identity and Update Identity).

  • v2 API: Add is_merchant field to the Identity API (Update Identity, Get Identity, List Identities).

  • v2 API: All metadata specified when creating a crypto deposit address is now inherited by deposit activities.

  • v2 API: Add optional is_merchant boolean field to the Create Identity request body and the List Identities, Create Identity, Get Identity and Update Identity responses.

  • v2 API: Add new attribute compatible_crypto_networks to the Create Deposit Address and List Deposit Addresses API responses. This field contains the compatible networks with the created or already existing deposit address.

  • v2 API: Add Insufficient Funds 403 error response to Create Fiat Withdrawal endpoint.

  • v2 API: Add new Fiat Transfer APIs which allow for automatic funding and withdrawal of fiat in a Paxos account.

  • v1 API, v2 API: Update REST Transfer API Rate Limit to 20 requests per second.
    • /v1/transfers/peer
    • /v1/transfers/profile
    • /v1/crypto-withdrawals
    • /v2/transfer/internal
    • /v2/transfer/crypto-withdrawals

  • v1 API, v2 API: The address1, city and province fields are no longer explicitly marked as required in the MailingAddress object. The v1 API CreateBankAccount endpoint and the v2 API Create Fiat Account and Update Fiat Account endpoints will continue to validate these fields if they exist.

  • Sandbox: PYUSD trading pairs are available in the Sandbox environment for REST and FIX users. All relevant endpoints support PYUSD-based trading pairs (for example, BTC:PYUSD and ETH:PYUSD among other). Contact Support for details.

  • v2 API: Add optional field self_match_prevention_id to Create Order. This field is used to prevent matching against an opposite side order submitted by the same Crypto Brokerage customer. If this field is not submitted, an order that matches against another order submitted by the same customer will cancel the original resting order.

  • v2 API: Enable HRQ users to buy and sell PYUSD using the Create Quote Execution endpoint. Allow all HRQ users to retrieve PYUSD using the List Quotes endpoint.
  • v2 API: Add PYUSD to the List Historical Prices endpoint.
  • v1 API: Enable PYUSD withdrawal. All PYUSD withdrawals debit USD balance only. Enable USD deposit auto-conversion to PYUSD withdrawal.
  • v2 API: Enable PYUSD withdrawals using the Transfers API with the option to debit USD balance. Add values asset=PYUSD and balance_asset=USD to the Create Crypto Withdrawal request.
  • Wallet UI: Enable PYUSD withdrawals. All PYUSD withdrawals debit USD balance only. Enable USD deposit Auto-Transfer to PYUSD withdrawal.
  • Docs: Add sourcing and implementation information to the Paxos Documentation.

  • v2 API: Add assets=PYUSD query parameter to List Profile Balances. Add asset=PYUSD path parameter to Get Profile Balances. Add ”asset”: “PYUSD” to Create Sandbox Deposit request body schema. Add PYUSD to properties base_asset, quote_asset, commission_asset and rebate_asset for the List Executions, List Quotes, List Quote Executions, Create Quote Execution and Get Quote Execution endpoints. About PYUSD.

  • V2 API: Add a default of 100 results to the limit query parameter and restrict the maximum page limit to 1,000 for the Paxos v2 API List Deposit Addresses service. Learn more.

  • v2 API: Add error code MARKET_CONDITIONS_PREVENTED_EXECUTION to Create Order response.
  • FIX: Add additional detailed failure reason (tag 58) Market conditions have invalidated this order.