# Why does API say this goal isn't integery?

**URL:** <https://forum.beeminder.com/t/why-does-api-say-this-goal-isnt-integery/10827>\
**Category:** Bugabee\
**Created:** [February 17, 2023, 3:55pm UTC](https://forum.beeminder.com/t/why-does-api-say-this-goal-isnt-integery/10827 "2023-02-17T15:55:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![narthur](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/narthur/32/5113_2.png) [@narthur](https://forum.beeminder.com/u/narthur)\
**Post date:** [February 17, 2023, 3:55pm UTC](https://forum.beeminder.com/t/why-does-api-say-this-goal-isnt-integery/10827/1 "2023-02-17T15:55:53Z")

</div>

This goal:

[https://www.beeminder.com/narthur/tr-cards](https://www.beeminder.com/narthur/tr-cards)

Has this setting:

![Screenshot 2023-02-17 at 10.55.32 AM](https://us1.discourse-cdn.com/flex019/uploads/beeminder/original/2X/d/d08964305df98ee5255725ddd157280a96748959.png)

So why does the API return `integery: false` for this goal?

Also, would be nice to be able to get the specific display precision selected via the API.

---

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\
**Post date:** [February 19, 2023, 1:49pm UTC](https://forum.beeminder.com/t/why-does-api-say-this-goal-isnt-integery/10827/2 "2023-02-19T13:49:00Z")

</div>

Because it’s not flagged as integery, it just has a display quantum of 1.

Besides which, integery is deprecated and shanaqui once expressed a suspicion that it’d behave badly alongside setting the display precision.

---

<div class="post-metadata">

**Author:** ![narthur](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/narthur/32/5113_2.png) [@narthur](https://forum.beeminder.com/u/narthur)\
**Post date:** [February 19, 2023, 2:12pm UTC](https://forum.beeminder.com/t/why-does-api-say-this-goal-isnt-integery/10827/3 "2023-02-19T14:12:33Z")

</div>

Hmm, ok. Any chance beeminder could run a migration from the one setting to the other and then just define integery in the api as `precision == "1"` or are there differences between how the two settings work that I don’t understand?