# Adding command line tools support for user api keys

**URL:** https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803
**Category:** Development
**Created:** [12월 6, 2018, 11:21오후 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803 "2018-12-06T23:21:13Z")
**Posts on this page:** 4
**Page:** 2

<div class="post-metadata">

### Author: ![vsoch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vsoch/32/124967_2.png) [@vsoch](https://meta.discourse.org/u/vsoch)
#### Post date: [12월 21, 2018, 3:40오후 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803/21 "2018-12-21T15:40:26Z")

</div>

Thanks @fitz! I can confirm that I can get a token with the helpme client I’m developing - should it be a string on multiple lines that we join by newline or just empty space (to generate one long string)?

Currently, I’m sending the api\_username and api\_token as part of the body (in data) and the requests that I made previously (using my Dockerized discourse with an admin key) are returning 403, Forbidden. Is your instance expecting a different post type (perhaps in headers or something different?) Or am I not parsing the key from the web interface correctly?

I’m overall wondering how the public key helps in this interaction. I’m guessing that since I’m logged into the discourse instance in my browser, an association is made between my login and the token that is generated? Didn’t we want to do some kind of token generation and/or using a key to sign, encrypt, and send, and then the server decodes?

---

<div class="post-metadata">

### Author: ![cfitz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cfitz/32/126431_2.png) [@cfitz](https://meta.discourse.org/u/cfitz)
#### Post date: [1월 1, 2019, 7:28오후 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803/22 "2019-01-01T19:28:37Z")

</div>

Ok,  
We put together a PR here  
[https://github.com/discourse/discourse/pull/6840](https://github.com/discourse/discourse/pull/6840)

Hope this helps.

---

<div class="post-metadata">

### Author: ![vsoch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vsoch/32/124967_2.png) [@vsoch](https://meta.discourse.org/u/vsoch)
#### Post date: [1월 1, 2019, 8:11오후 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803/23 "2019-01-01T20:11:52Z")

</div>

![pusheen-typing](https://global.discourse-cdn.com/meta/original/3X/7/0/70f327a398e2c4b743d4246e2b5b0d051971315b.gif) Programmer Pusheen, +1!

---

<div class="post-metadata">

### Author: ![vsoch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vsoch/32/124967_2.png) [@vsoch](https://meta.discourse.org/u/vsoch)
#### Post date: [1월 4, 2019, 3:53오후 UTC](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803/24 "2019-01-04T15:53:35Z")

</div>

Thanks everyone for the enormous effort here! We’ve merged the discourse PR, along with the helpme client ([Client Challenge](https://pypi.org/project/helpme/0.0.36/)) and I’m really excited to get a deployment underway!

[Previous page](https://meta.discourse.org/t/adding-command-line-tools-support-for-user-api-keys/103803.md?page=1)