/compute/position

Base URL https://api.babylon.app/v1

POST /compute/position

Compute current security positions across a Babylon segment. The calculation excludes SIPP and RA accounts and considers entries settling on or before valueDate.

JSON request body

  • segmentLedger (required) — identifier of the Babylon segment to analyse.
  • valueDate (optional) — latest settlement date to include, in YYYY-MM-DD format; defaults to the current date.

Example request

POST /compute/position
Content-Type: application/json
{
  "segmentLedger": "MyGBSegment",
  "valueDate": "2026-07-22"
}

Example response — 200

{
  "name": "Position",
  "description": "MyGBSegment - accountTypes excluding [SIPP, RA]",
  "columns": ["bourseSymbol", "quantityAdj", "costBasis", "unitCost"],
  "columnTypes": {
    "quantityAdj": "Decimal",
    "costBasis": "Decimal",
    "unitCost": "Decimal"
  },
  "rows": [
    {
      "bourseSymbol": "LSE:VUSA",
      "quantityAdj": "150",
      "costBasis": "45000",
      "unitCost": "300"
    }
  ]
}

For CSV, send Accept: text/csv:

POST /compute/position
Accept: text/csv
Content-Type: application/json
{
  "segmentLedger": "MyGBSegment",
  "valueDate": "2026-07-22"
}
BourseSymbol,QuantityAdj,CostBasis,UnitCost
LSE:VUSA,150,45000,300

GET /compute/position

GET uses the same operation parameters in the query string.

Query parameters

  • segmentLedger (required) — identifier of the Babylon segment to analyse.
  • valueDate (optional) — latest settlement date to include, in YYYY-MM-DD format.

Example request

GET /compute/position?segmentLedger=MyGBSegment&valueDate=2026-07-22

The response has the same shape as the POST response. Send Accept: text/csv to receive CSV.

Further reading

← Back to API