Skip to main content
POST
/
investments
/
transactions
/
{id}
/
cancel
Cancel a portfolio asset transaction
curl --request POST \
  --url https://{host}/investments/transactions/{id}/cancel \
  --header 'Authorization: Bearer <token>' \
  --header 'x-user-id: <x-user-id>'
{
  "id": "64f5b3137fb3fc001234abce",
  "category": "AssetTransaction",
  "status": "Cancelled",
  "portfolioTransactionCategory": "buy",
  "owner": "64f0c51e7fb3fc001234abcd",
  "portfolio": "64f0c51e7fb3fc001234abcd",
  "consideration": {
    "currency": "EUR",
    "amount": 250.5
  },
  "orders": [
    {
      "id": "64f5b3137fb3fc001234abcf",
      "isin": "US0378331005",
      "side": "Buy",
      "status": "Cancelled",
      "consideration": {
        "currency": "EUR",
        "amount": 250.5
      }
    }
  ]
}

Authorizations

​
Authorization
string
header
required

Auth0-issued access token that includes the scopes listed for the endpoint.

Headers

​
x-user-id
string
required

User identifier for the M2M client to specify which user's data to access.

Pattern: ^[a-f0-9]{24}$

Path Parameters

​
id
string
required

Transaction identifier (MongoDB ObjectId)

Pattern: ^[a-f0-9]{24}$

Response

Transaction cancelled successfully

Asset transaction enriched with display-ready fields.

​
id
string
required
​
category
enum<string>
required
Available options:
AssetTransaction
​
status
string
required

Current transaction status (Pending, PendingGift, Settled, etc.).

​
orders
object[]
required
​
portfolioTransactionCategory
enum<string>
Available options:
update,
buy,
sell
​
owner
string

User identifier owning the transaction.

​
portfolio
string

Portfolio identifier associated with the transaction.

​
consideration
object
​
executionWindow
object

Execution windows separated by asset category (matches domain ExecutionWindowsType)

​
fees
object