# What happened. In your own code.

> New members, comments, paid plans, sends and agents' posts, as JSON with a staff key. Every event of the audit log too, for owners and admins.

The Notifications screen answers as JSON. **Your code reads the same list the screen shows**: new members, comments, paid plans, sends and the posts your agents publish.

## By hand, in the admin

1. Make a staff key in **Settings › API** or **Settings › MCP setup**, under **Your keys**.
2. Ask /pixel/notifications.json with the key as a Bearer token. Fifty come a page, newest first.
3. Narrow the list with an area: readers, conversation, posts, newsletters, team, site or payments.
4. Read each notification's kind, its sentence, the record it is about and the facts of the moment.
5. As an owner or admin, read every event at /pixel/settings/audit-log.json, by area or by who did it.

## With your agent


No tool on the MCP server reads the notifications. Your agent's work shows in them: a post an agent publishes is a notification for everyone, and the audit log names the key or app it used.

## Examples

- **Paid members in the team chat.** A newsletter's script asks for the readers area every five minutes and **posts each new paid member to the team's chat**.
- **A weekly digest.** A magazine reads the conversation area each Monday and mails its editors the week's comment count.
- **An eye on the agents.** A newsroom reads the posts area for every post an agent published, with the agent's name and the person who connected it.

## Questions

### Can I read PixelGlass notifications as JSON?

Yes. Ask /pixel/notifications.json with a staff key. You get the list the Notifications screen shows that key's person, fifty a page.

### Does reading the JSON mark notifications read?

No. Only the screen marks them read, so a script never takes them from the person.

### How far back do notifications go?

The list shows the last 90 days. The audit log keeps every event for a year.

### Are readers' addresses in a notification?

Never. A notification names the record it is about, and your code asks for the member by that id when it needs them.

### Does PixelGlass have webhooks?

Not yet. Read the list on a schedule. A kind's name never changes, so your code can rely on it.

### Who can read the audit log as JSON?

The owner and the admins, with their own staff keys. Each person reads the notifications their role may see.

## See also

- [Make a staff key](https://pixelglass.co/guides/make-a-staff-key): A staff key acts as you, inside your role, on the admin's JSON and the MCP server. Make one, copy it once, remove it to close it.
- [Sync members from your app](https://pixelglass.co/guides/sync-members-from-your-app): Keep your app's users and your PixelGlass members in step over the admin's JSON: find by address, add, change, label, and change many at once.
- [Use PixelGlass as a headless CMS](https://pixelglass.co/guides/use-pixelglass-as-a-headless-cms): Add .json to any address of your site and read posts, pages, tags and authors with a content key. Write in PixelGlass, show it in your own code.
- [Developer API](https://pixelglass.co/features/developers): Read your site as JSON, sync members from your app, sign readers in with your own accounts, and run it all from an agent. Webhooks are coming soon.
- [Every guide](https://pixelglass.co/guides)
- [Pricing](https://pixelglass.co/pricing): every feature on every plan, 14 days free
- [Create your site](https://pixelglass.co/signup)