# Is there a standard implementation for webdev based tag read?

**URL:** <https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091>\
**Category:** Ignition\
**Tags:** ignition83, webdev\
**Created:** [February 20, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091 "2026-02-20T14:59:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [February 20, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091/1 "2026-02-20T14:59:12Z")

</div>

Title –

Looking to read tags via API, I’m glad to roll my own if I need to but I figured i’d check if there was a standardized library/resource people would point to.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 20, 2026, 3:12pm UTC](https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091/2 "2026-02-20T15:12:32Z")

</div>

I haven't seen one I like. Key things I'd include but haven't seen anyone do:

- Accept a **list** of tag paths in a POST, not just a single tagpath in the query params of a GET.

- Enforce tag access restrictions

- Include a method to also query history and deliver efficiently (column-wise, not row-wise).

---

<div class="post-metadata">

**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\
**Post date:** [February 20, 2026, 7:31pm UTC](https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091/3 "2026-02-20T19:31:10Z")

</div>

Why post for list instead of url encoded get?

It’s a synchronous read, that seems like it should be a GET by rest rules?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 20, 2026, 7:39pm UTC](https://forum.inductiveautomation.com/t/is-there-a-standard-implementation-for-webdev-based-tag-read/114091/4 "2026-02-20T19:39:10Z")

</div>

GET responses are cacheable by default, which immediate disqualifies it as a sane HTTP verb to use for reading a tag.

Using a query parameter might be okay if your API accepts a read for a single tag path, but it's no good if you want to accept multiple.