fund_nav

Monthly NAV/flows series for one CNPJ, oldest first. Default window (p_to NULL) ends at the family’s latest COMPLETE period per mv_period_completeness; an explicit p_to serves the window verbatim, partial months included. Row cap: more than 1000 rows RAISES 22023 (never trimmed) unless p_after pages: ” = first page, then the last row’s period as ‘YYYY-MM-DD’. PAGING REQUIRES p_entity_type — one CNPJ can file under two families in the same month (385 do), so a bare period is unique only within one family; whole-result mode serves both and labels each row. period keeps each family’s own date convention: fi, fii and fiagro rows are dated the FIRST of the month (an fi row carries the last daily report filed in that month, so 2026-09-01 holds September’s closing NAV), fidc rows the month-END (2026-08-31), fip rows 31 December of the year; the trailing period_month is the same month as api.panel keys it (first of month), equal to period for fi, fii and fiagro. Columns are per family (fact_fund_monthly arms): fi files quota, quotaholders, inflows, redemptions; fidc and fiagro file delinquency; fii files quotaholders, monthly_yield, assets; fip files nav only — a null outside that list is not applicable, not missing (catalog().applicability). fidc delinquency is filed from 2013-01, null for a fund with no tab VI row before 2020-11 and on every row from 2020-11 (regime break; catalog().regime_breaks).

Row cap. A window producing more than 1000 rows raises SQLSTATE 22023 naming this function. Nothing is trimmed to fit — PostgREST would silently cut the response at 1000 and a cut-short series is indistinguishable from one that simply ends. This function pages: send p_after = "" for the first page, then the key copied from the last row; a page shorter than 1000 is the last. p_after = null is whole-result mode, which is what refuses.

POST /rpc/fund_nav

fund_nav

cURL

curl --request POST \
  --url https://zcjbtpxuhdekpwcxmepn.supabase.co/rest/v1/rpc/fund_nav \
  --header 'Content-Type: application/json' \
  --header 'apikey: <api-key>' \
  --data '
{
  "p_cnpj": "<string>",
  "p_from": "2019-01-01",
  "p_to": null,
  "p_entity_type": null,
  "p_after": null
}
'

200

[
  {
    "cnpj": "<string>",
    "period": "2023-12-25",
    "entity_type": "<string>",
    "nav": 123,
    "quota": 123,
    "quotaholders": 123,
    "delinquency": 123,
    "monthly_yield": 123,
    "inflows": 123,
    "redemptions": 123,
    "assets": 123,
    "period_month": "2023-12-25"
  }
]

Authorizations

apikey · string · header · required

The publishable key (sb_publishable_…), on every request. It is NOT a JWT — sending it as Authorization: Bearer is rejected as an invalid JWT. It identifies the project, not you, and maps to the Postgres anon role.

Body

application/json

p_cnpj · string | null · required

p_from · string<date> | null · default: 2019-01-01

Defaults to '2019-01-01'::date.

p_to · string<date> | null

Defaults to NULL::date.

p_entity_type · string | null

Defaults to NULL::text.

p_after · string | null

Defaults to NULL::text.

Response

200

application/json

The result set, oldest first. An unknown id is an empty array, not a 404 and never a guessed value.

cnpj · string | null

period · string<date> | null

entity_type · string | null

nav · number | null

quota · number | null

quotaholders · integer<int32> | null

delinquency · number | null

monthly_yield · number | null

inflows · number | null

redemptions · number | null

assets · number | null

period_month · string<date> | null