Categories and figures

POST/v1/categories/{id}/recompute

Work a category's summary figures out again and answer with them.

What it does

You rarely need this. Every figure the API answers with is worked out when you read it, from the newest report, its settings, the suppliers and the exceptions as they are at that moment. This call refreshes the stored summary the app's shop page shows and forgets this report's cached model, then answers with the fresh summary.

Who may call it

A key whose maker's role holds figures (see the figures), after the fence, for the shop or category it names.

Request

HTTP
POST https://panlytics.net/api/v1/categories/{id}/recompute

Parameters

NameInTypeRequiredWhat it is
idpathintegerYesThe category's id.
AuthorizationheaderstringYesBearer, a space, then the key.

Example request

curl -X POST https://panlytics.net/api/v1/categories/40/recompute \
  -H "Authorization: Bearer $PANLYTICS_KEY"

Response

200: The answer, as JSON.

FieldTypeAlways thereWhat it is
categoryIdintegerYesThe category the figures are for.
reportIdintegerYesThe report the figures were worked out from.
salesEurnumberYesSales over the report's period, in euros.
missedSalesEurnumberYesSales you missed: what people came for while the shelf was empty.
wasteEurnumberYesWhat was thrown away over the report's period, in euros.
computedAtstring (ISO 8601)YesWhen these figures were worked out, in UTC.

Example response

200
{
  "categoryId": 40,
  "reportId": 311,
  "salesEur": 48210.5,
  "missedSalesEur": 1310.2,
  "wasteEur": 420.75,
  "computedAt": "2026-10-25T09:31:00.000Z"
}

Errors

A refusal is JSON with a code, a sentence in error, and a requestId when the fault is ours. Read the code, not the sentence. Every code is listed on Errors.

StatusCodeWhenWhat to do
400api.invalidA path id, a query parameter, a header or a body field is missing or not valid. detail names the field.Read that endpoint in the API reference, correct the field and call again.
401api.key_missingThe call had no Authorization header.Send the key in the Authorization header as Bearer, then call again.
401api.key_refusedThe key is wrong, revoked, past its end, or its maker or company no longer allows it (developer mode off, the maker removed or switched off, or the maker's role lost the developer ability).Ask the person who gave you the key to make a new one.
401api.wrong_key_kindThis key does not open these endpoints.Use the key these endpoints were made for, or ask the person who gave you the key.
403refusedThe key's maker may not do this here: their role lacks the ability, or the shop or category is outside their reach.Ask the CEO for a role that allows it, or call it for a shop or category the role reaches.
403auth.not_freshThis step needs you to prove it is you.Confirm your password or passkey, then try again.
404not_found.saidNothing with that id in the key's company. An id of another company answers the same.Check the id. List the shop or category it belongs to and take the id from there.
409report.noneThere is no report yet to work from.Upload a report first, with POST /v1/shops/{id}/reports.
429api.rate_limitedThe key made more than 120 calls in this minute. Wait the seconds in Retry-After.Wait the seconds in Retry-After, then call again.
500serverSomething failed on our side. The answer carries a requestId to quote.Try again in a minute; if it keeps happening, report it.
503developer.unavailableAPI keys are not set up on this deployment yet.Report it, and we will switch them on.