Remote Row Operations

These routes serve msm.client's remote backend (ADR 0047, decision 2). An application that selects the remote backend runs msm.api row class methods here instead of holding MetaTables grants on mainsequence.markets. See Client for the application side.

Describe Row Operations

GET /api/v1/rows/

Lists every row resource (asset, account, portfolio, currency-spot, index, calendar ...), its row class and each operation with its name, whether it writes and its Python signature.

Run A Row Operation

POST /api/v1/rows/{resource}/{operation}/

Request:

{"arguments": {"unique_identifier": "ACME", "asset_type": "equity"}}

Response:

{"result": {"uid": "...", "unique_identifier": "ACME", "asset_type": "equity"}}

operation is a public class method of the row class registered as resource, for example upsert, get_by_uid, get_many_by_unique_identifier, filter, list_related_meta_tables or CurrencySpot.upsert's upsert. arguments are its named arguments; a Pydantic payload is sent as an object with only the fields that were set. The route runs the method on this deployment's runtime backend and returns its result as JSON. There is no generic query: filter and count accept equality, <field>_contains, <field>__in and <field>__gte/__gt/__lte/__lt filters on the row model's own fields only.

Writes (create, upsert, update, delete, add, bulk_delete, add_portfolio, remove_portfolio, replace_memberships, create_batch, create_from_pandas_calendar, reconcile_dataset_availability, upsert_many, add_many, create_index_curve_selection, upsert_index_curve_selection, publish, register, register_signal, unregister, unregister_signal, reconcile, activate_definition, retire_definition) run through registry_write, which records who made them. A table row class's delete runs the resource's service delete with its preflight checks and exists only for asset, asset-category, calendar, index, portfolio and portfolio-group. Composites that implement delete themselves (curve, pricing-market-data-set, the binding resources) run it like any other operation.

The resources include the msm_portfolios.api metadata rows (signal-metadata, portfolio-metadata, rebalance-strategy-metadata) and the msm_pricing.api composites (curve, curve-building-details, index-convention-details, pricing-market-data-set, pricing-market-data-set-binding, pricing-market-data-set-curve-binding, asset-current-pricing-details, asset-pricing-details).