# Poison - Encoding issue (tuples)

**URL:** <https://forum.elixirforum.com/t/poison-encoding-issue-tuples/55382>\
**Category:** Questions\
**Tags:** poison, troubleshooting, learning-elixir, elixir-poison, http-poison\
**Created:** [April 19, 2023, 10:40am UTC](https://forum.elixirforum.com/t/poison-encoding-issue-tuples/55382 "2023-04-19T10:40:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![cloudytoday](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/c/ecc23a/32.png) [@cloudytoday](https://forum.elixirforum.com/u/cloudytoday)\
**Post date:** [April 19, 2023, 2:39pm UTC](https://forum.elixirforum.com/t/poison-encoding-issue-tuples/55382/3 "2023-04-19T14:39:08Z")

</div>

It should work, unless you made some typos somewhere or haven’t recompiled the project so that the protocols could get re-consolidated again. You can also try Jason instead of Posion:

```elixir
iex(1)> t = {:propose, "Appeltaart"}
{:propose, "Appeltaart"}
iex(2)> Jason.encode t
{:error,
 %Protocol.UndefinedError{
   protocol: Jason.Encoder,
   value: {:propose, "Appeltaart"},
   description: "Jason.Encoder protocol must always be explicitly implemented"
 }}
iex(3)> Jason.encode (Tuple.to_list t)
{:ok, "[\"propose\",\"Appeltaart\"]"}

```

Although, as Ben noted above, it all depends on what kind of JSON you want to see at the end of the day.

---

_[View the full topic](https://forum.elixirforum.com/t/poison-encoding-issue-tuples/55382)._