Sign in

v2

latestOpenAPI 3.0.3Apache 2.02026-08-0715707.5 MB
Securities Transfers

Create securities transfer

Create securities transfer

post/securities_transfers

Headers

idempotency-keystring uuid required
Example:ccb07f42-4104-44ad-8e1f-c660bb7b269c

A UUID to be used as an idempotency key. This prevents a duplicate request from being replayed. https://docs.upvest.co/documentation/concepts/api_concepts/idempotency

Request body

direction'INCOMING' | 'OUTGOING' required

Direction of the securities transfer

  • INCOMING - Securities transfer is incoming to the user.
  • OUTGOING - Securities transfer is outgoing from the user.
instrument_idstring required

ISIN or other identity (depends on instrument_id_type) of the security to be transferred.

instrument_id_type'ISIN' required

Type of the instrument_id

  • ISIN - International Securities Identification Number
quantitystring required

The quantity of instrument to move in or out. The value supported is maximum 15 digits including decimal place. Note: For INCOMING the end user ensures that they don't sell their instruments on the counter-broker to enable smooth transfer of their instruments on Upvest platform.

transfer_type'NO_OWNER_CHANGE' required

Type of the securities transfer

  • NO_OWNER_CHANGE - No change of ownership.
user_idstring uuid required

User unique identifier.

account_idstring uuid required

Account unique identifier.

place_of_settlementstring

Business Identifier Code (also known as SWIFT-BIC, BIC, SWIFT ID or SWIFT code) ISO 9362.

settlement_referencestring required

Unique identifier of the securities transfer set by API consumers. Useful for API consumers to build special logic on top of it. NOTE: For automatic incoming transfers where API users will subscribe to the corresponding webhook, the value is set by Upvest! TIP: For non-live environment if you prefix the reference with AUTO your transfer gets through all lifecycle states.

trade_datestring date

Optional forecast date when the trade takes place. If provided, usually T+1 is sufficient. Depending on the market this means valid working days. Date in YYYY-MM-DD format.

settlement_datestring date

Optional forecast date when the settlement takes place. If provided, usually T+2 is sufficient or trade_date + 1. Depending on the market this means valid working days. Date in YYYY-MM-DD format.

order_datestring date

Optional date when the transfer request was received from the end user. If omitted, Upvest defaults order_date to the transfer's created_at timestamp. The regulatory deadline runs from this date. Date in YYYY-MM-DD format.

Response

Securities Transfer created

idstring uuid required

Securities transfer request unique identifier.

created_atstring date-time required

Date and time when the resource was created. RFC 3339-5, ISO8601 UTC

updated_atstring date-time required

Date and time when the resource was last updated. RFC 3339-5, ISO8601 UTC

direction'INCOMING' | 'OUTGOING' required

Direction of the securities transfer

  • INCOMING - Securities transfer is incoming to the user.
  • OUTGOING - Securities transfer is outgoing from the user.
status'NEW' | 'PROCESSING' | 'SETTLED' | 'CANCELLED' required

Status of the securities transfer

  • NEW - Securities transfer is created but not started processing.
  • PROCESSING - Securities transfer is in processing.
  • SETTLED - Securities transfer was successfully settled.
  • CANCELLED - Securities transfer was cancelled.
transfer_type'NO_OWNER_CHANGE' required

Type of the securities transfer

  • NO_OWNER_CHANGE - No change of ownership.
instrument_idstring required

ISIN or other identity (depends on instrument_id_type) of the security to be transferred.

instrument_id_type'ISIN' required

Type of the instrument_id

  • ISIN - International Securities Identification Number
quantitystring required

The quantity of instrument to move in or out.

quantity_settledstring

The quantity of instruments settled.

user_idstring uuid required

User unique identifier.

account_idstring uuid required

Account unique identifier.

place_of_settlementstring

Business Identifier Code (also known as SWIFT-BIC, BIC, SWIFT ID or SWIFT code) ISO 9362.

settlement_referencestring required

Unique identifier of the securities transfer set by API consumers. Useful for API consumers to build special logic on top of it. NOTE: For automatic incoming transfers where API users will subscribe to the corresponding webhook, the value is set by Upvest!

trade_datestring date required

The forecast date when the trade takes place. Date in YYYY-MM-DD format.

settlement_datestring date required

The forecast date when the settlement takes place. Date in YYYY-MM-DD format.

actual_settlement_datestring date

The date when the transfer settled, only known in SETTLED status. Date in YYYY-MM-DD format.

order_datestring date

Optional. Date the transfer request was received from the end user. The regulatory deadline runs from this date. Date in YYYY-MM-DD format.

delay_reason'COUNTERPARTY_NOT_INSTRUCTING' | 'COUNTERPARTY_NOT_RESPONDING' | 'COUNTERPARTY_DOES_NOT_AGREE_TO_DELIVERY_DETAILS' | 'COUNTERPARTY_NOT_ACCEPTING'

Categorised reason why a securities transfer is delayed past the regulatory deadline.

  • COUNTERPARTY_NOT_INSTRUCTING - The counterparty has not yet instructed the transfer.
  • COUNTERPARTY_NOT_RESPONDING - The counterparty is not responding.
  • COUNTERPARTY_DOES_NOT_AGREE_TO_DELIVERY_DETAILS - The counterparty does not agree to the delivery details.
  • COUNTERPARTY_NOT_ACCEPTING - The counterparty is not accepting the transfer.