Notifications and issues

GET/v1/notifications

The newest notifications of the person who made the key, as the bell shows them.

What it does

Only news about the shops the key reaches. The notice that an AI signed in stays unread until the person reads it in the app.

Who may call it

Any live key may call it. It reads only what the key's maker may already see about themselves.

Request

HTTP

GET https://panlytics.net/api/v1/notifications

Parameters

Name	In	Type	Required	What it is
`Authorization`	header	string	Yes	Bearer, a space, then the key.

Example request

curl https://panlytics.net/api/v1/notifications \
  -H "Authorization: Bearer $PANLYTICS_KEY"

import os

import requests

response = requests.get(
    "https://panlytics.net/api/v1/notifications",
    headers={"Authorization": f"Bearer {os.environ['PANLYTICS_KEY']}"},
    timeout=60,
)
response.raise_for_status()
print(response.json())

const response = await fetch("https://panlytics.net/api/v1/notifications", {
  headers: {
    Authorization: `Bearer ${process.env.PANLYTICS_KEY}`,
  },
});
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
`unread`	integer	Yes	How many are unread.
`notifications[]`	object[]	Yes	The newest few, as the bell shows them.
`notifications[].id`	string	Yes	The notification's id.
`notifications[].kind`	string	Yes	What kind of news it is.
`notifications[].subject`	string	Yes	The news, in one sentence.
`notifications[].href`	string or null	Yes	The page in the app it links to, or null.
`notifications[].createdAt`	string (ISO 8601)	Yes	When it was sent, in UTC.
`notifications[].readAt`	string (ISO 8601) or null	Yes	When it was read, or null.

Example response

200

{
  "unread": 1,
  "notifications": [
    {
      "id": "n_9f2",
      "kind": "report.read",
      "subject": "Dairy's new report was read.",
      "href": "/category/40",
      "createdAt": "2026-10-25T09:00:00.000Z",
      "readAt": null
    }
  ]
}

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
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.
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.