The sheet and exceptions

POST/v1/categories/{id}/sheet-edits

Change figures in a category's newest report, as the Sheet page's edits do.

What it does

Each edit names a product, an editable column and the new value. The batch is saved in one write, every figure is worked out again, and the change is written to the audit log. Send the report's updatedAt so an edit made since is never overwritten.

Who may call it

A key whose maker's role holds sheet (edit the sheet and upload a report), after the fence, for the shop or category it names.

Request

HTTP

POST https://panlytics.net/api/v1/categories/{id}/sheet-edits

Parameters

Name	In	Type	Required	What it is
`id`	path	integer	Yes	The category's id.
`Authorization`	header	string	Yes	Bearer, a space, then the key.

Body

Sent as application/json.

Field	Type	Required	What it is
`edits[]`	object[]	Yes	The edits, 1 to 500, saved together or not at all.
`edits[].ean`	string	Yes	The product's id.
`edits[].field`	string	Yes	An editable column's key.
`edits[].value`	number	Yes	The new value. Only margin may be below zero.
`updatedAt`	string (ISO 8601)	No	The report's `updatedAt` as you read it. When it has changed since, the save answers 409 and changes nothing.

Example request

curl -X POST https://panlytics.net/api/v1/categories/40/sheet-edits \
  -H "Authorization: Bearer $PANLYTICS_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "edits": [
    {
      "ean": "6410000000017",
      "field": "stockPcs",
      "value": 24
    }
  ],
  "updatedAt": "2026-10-25T09:00:00.000Z"
}'

import os

import requests

response = requests.post(
    "https://panlytics.net/api/v1/categories/40/sheet-edits",
    headers={"Authorization": f"Bearer {os.environ['PANLYTICS_KEY']}"},
    json={
      "edits": [
        {
          "ean": "6410000000017",
          "field": "stockPcs",
          "value": 24
        }
      ],
      "updatedAt": "2026-10-25T09:00:00.000Z"
    },
    timeout=60,
)
response.raise_for_status()
print(response.json())

const response = await fetch("https://panlytics.net/api/v1/categories/40/sheet-edits", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.PANLYTICS_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "edits": [
      {
        "ean": "6410000000017",
        "field": "stockPcs",
        "value": 24
      }
    ],
    "updatedAt": "2026-10-25T09:00:00.000Z"
  }),
});
if (!response.ok) throw new Error(`Panlytics answered ${response.status}`);
console.log(await response.json());

Response

200: The answer, as JSON.

Field	Type	Always there	What it is
`reportId`	integer	Yes	The report the edits were saved to.
`saved`	integer	Yes	How many edits were saved.

Example response

200

{
  "reportId": 301,
  "saved": 1
}

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.

Status	Code	When	What to do
400	`api.invalid`	A 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.
400	`bad_request.said`		Change it and try again.
401	`api.key_missing`	The call had no Authorization header.	Send the key in the Authorization header as Bearer, then call again.
401	`api.key_refused`	The 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.
401	`api.wrong_key_kind`	This key does not open these endpoints.	Use the key these endpoints were made for, or ask the person who gave you the key.
403	`refused`	The 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.
403	`auth.not_fresh`	This step needs you to prove it is you.	Confirm your password or passkey, then try again.
403	`refused.demo`	The key belongs to a shared demo account, which may not change anything.	Use a key made in a real company account.
404	`not_found.said`	Nothing 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.
409	`report.none`	There is no report yet to work from.	Upload a report first, with POST /v1/shops/{id}/reports.
409	`api.stale`	The category changed after the `updatedAt` you sent.	Read it again, then send your change with the new updatedAt.
429	`api.rate_limited`	The key made more than 120 calls in this minute. Wait the seconds in Retry-After.	Wait the seconds in Retry-After, then call again.
500	`server`	Something failed on our side. The answer carries a requestId to quote.	Try again in a minute; if it keeps happening, report it.
503	`developer.unavailable`	API keys are not set up on this deployment yet.	Report it, and we will switch them on.