API

Welcome to the Babylon API documentation.

The API provides programmatic access to five core areas:

  • Holdings — saved segment ledgers, cash ladders, bond ladders and savings sets.
  • Reference — current and historic security listings and corporate-action splits.
  • Compute — positions, capital gains and cash-flow calculations applied to segment ledgers and ladders.
  • Extract — extraction of segment entries from CSV, Excel, PDF, email and natural-language sources.
  • System — service availability information.

Many endpoints return a tabular JSON object with table metadata, a list of columns and row objects. Plain table responses can also be requested as CSV where the endpoint states that this is supported.

Global rules

  • All requests require Authorization: Bearer <api_key>; authentication is omitted from the examples.
  • GET requests supply operation parameters in the query string.
  • POST requests supply operation parameters in a JSON request body unless an endpoint states otherwise.
  • Responses are JSON by default.
  • For endpoints that return a plain table, request CSV with Accept: text/csv. The file-extraction endpoint also accepts "format": "csv" in its JSON body.
  • Tabular JSON uses the envelope name, description, columns, columnTypes and rows. Row field names are camel case. Decimal values are encoded as strings and identified in columnTypes.
  • Parameter names and output fields are endpoint-specific. format and columns are not universal parameters.

The two tabular source formats have their own detailed specifications:

The API is continually evolving, and this documentation will grow as endpoints and features are added.


Endpoints

Holdings

Reference

Compute

Extract

System

  • /system/status — Check whether the Babylon API service is available.