# \#api

**URL:** https://discourse.joplinapp.org/tag/api/26.md

[Latest](https://discourse.joplinapp.org/latest.md) · [Categories](https://discourse.joplinapp.org/categories.md) · [Tags](https://discourse.joplinapp.org/tags.md)

---

## [API documentation: add tag to note](https://discourse.joplinapp.org/t/api-documentation-add-tag-to-note/28837)

<div class="topic-metadata">

**Author:** [@Marph](https://discourse.joplinapp.org/u/Marph)\
**Replies:** 0\
**Last updated:** [28 December 2022 15:20 UTC](https://discourse.joplinapp.org/t/api-documentation-add-tag-to-note/28837 "2022-12-28T15:20:26Z")

</div>

I recently stumbled upon a small undocumented behavior of the data API when testing joppy. I guess this doesn't affect any real usecase, so it should be fine to leave it here as documentation. When adding an existing ta…

---

## [Joplin API - Token in HEADER vs Query parameters](https://discourse.joplinapp.org/t/joplin-api-token-in-header-vs-query-parameters/12573)

<div class="topic-metadata">

**Author:** [@foxmask](https://discourse.joplinapp.org/u/foxmask)\
**Replies:** 10\
**Last updated:** [3 June 2021 04:35 UTC](https://discourse.joplinapp.org/t/joplin-api-token-in-header-vs-query-parameters/12573 "2021-06-03T04:35:05Z")

</div>

Hi, Could it be possible to move the usage of the token from the query parameter to a HEADER like X\_JOPLIN\_TOKEN or something like that, which could be little be more secure and avoiding to be exposed by intermediaries …