# xmin and xmax via api

**URL:** <https://forum.beeminder.com/t/xmin-and-xmax-via-api/9031>\
**Category:** Tech\
**Created:** [February 22, 2021, 5:09pm UTC](https://forum.beeminder.com/t/xmin-and-xmax-via-api/9031 "2021-02-22T17:09:25Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![zzq](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/zzq/32/6471_2.png) [@zzq](https://forum.beeminder.com/u/zzq)\
**Post date:** [February 22, 2021, 9:55pm UTC](https://forum.beeminder.com/t/xmin-and-xmax-via-api/9031/3 "2021-02-22T21:55:32Z")

</div>

> [@eugeniobruno](#):
>
> 1. obtain a website cookie from [Beeminder API Reference](https://api.beeminder.com/#redirectuser)
> 2. GET the CSRF token from [beeminder](https://www.beeminder.com/gfredericks/goal_name)
> 3. POST the settings to [beeminder](https://www.beeminder.com/gfredericks/goal_name)

For what it’s worth, I’ve… actively considered doing this to add support in [altbee](https://altbee.aeonc.com/) for this and a few other similar things. I haven’t, yet, though altbee does do a simplified version of this (just the cookie, no need for a CSRF token) for getting the tags associated with each goal (briefly described [here](https://forum.beeminder.com/t/altbee-the-alternative-beeminder-web-interface/7315/35).)

Yeah, it’s hardly ideal—but it works, and if there are other feature in the future which I want to add to altbee that also need to work this way, well, I’ll probably go for it, CSRF token and all (though I can’t quite say I don’t have a few misgivings about it…)

---

_[View the full topic](https://forum.beeminder.com/t/xmin-and-xmax-via-api/9031)._