Results

Use the results endpoints to retrieve completed calculation outputs after submission.

GET /results is request-scoped and can be used whenever POST /portfolios returns a request_id. GET /results/accounts returns the latest live account results for the caller, including results written by batch processing.

GET/results?request_id=REQUEST_ID

Get results by request ID

Use this endpoint to fetch the result for any portfolio submission that returned a request_id. This includes synchronous and asynchronous responses from POST /portfolios.

Required query parameter:

Name
request_id
Type
string
Description
Request UUID returned by the original POST /portfolios submission.

cURL

curl -sSX GET "$C9_API_ENDPOINT/results?request_id=$REQUEST_ID" \
  -H "Authorization: Bearer $C9_API_SECRET"

If the original request was synchronous, GET /results?request_id=... can still be used to fetch the completed result by request ID.

Typical flow:

Submit a portfolio and capture the returned request_id
Poll GET /results?request_id=REQUEST_ID until the result is ready
Use the returned result payload in your application

GET/results/accounts

Get account results

Returns the latest live calculation for every account owned by the caller.

This endpoint is especially relevant after batch processing, because the batch workflow writes per-account outputs into the caller's live portfolio store.

cURL

curl -sSX GET "$C9_API_ENDPOINT/results/accounts" \
  -H "Authorization: Bearer $C9_API_SECRET"

Typical uses:

fetch the latest results for all live accounts
retrieve account-level outputs after a completed batch
filter the returned accounts down to the submitted account_code values from a specific batch

GET /results/accounts is not scoped to a single batch_id. After batch processing, your client should keep track of the submitted account_code values and filter the returned accounts accordingly.

Read the Batch processing guide