# Marcar notificações como lidas via API do Discourse

**URL:** https://meta.discourse.org/t/mark-notifications-as-read-from-discourse-api/113420
**Category:** Development
**Created:** [4 Abril , 2019 07:13 UTC](https://meta.discourse.org/t/mark-notifications-as-read-from-discourse-api/113420 "2019-04-04T07:13:31Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5 Abril , 2019 10:57 UTC](https://meta.discourse.org/t/mark-notifications-as-read-from-discourse-api/113420/4 "2019-04-05T10:57:00Z")

</div>

Anything you can do from the website you can do from the API per:

> [@Reverse engineer the Discourse API](https://meta.discourse.org/t/how-to-reverse-engineer-the-discourse-api/20576):
>
> Discourse is backed by a complete JSON api. Anything you can do on the site you can also do using the JSON api. The API is documented at [docs.discourse.org](https://docs.discourse.org). You can also use the [discourse\_api](https://github.com/discourse/discourse_api) Ruby gem as a client library. However, not every endpoint is documented. To determine how to do something with the JSON API here are some steps you can follow. Example: recategorize a topic. Go to a topic and start editing a category: Open Chrome dev tools, switch to the Network tab, select …

The problem here is that delegating this to clients is inherently unsafe. How do you have confidence the end users are even logged in to Discourse?

---

_[View the full topic](https://meta.discourse.org/t/mark-notifications-as-read-from-discourse-api/113420)._