# API key request

**URL:** <https://community.tempest.earth/t/api-key-request/4975>\
**Category:** Developers\
**Created:** [December 19, 2019, 5:20pm UTC](https://community.tempest.earth/t/api-key-request/4975 "2019-12-19T17:20:31Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruce](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/bruce/32/5826_2.png) [@bruce](https://community.tempest.earth/u/bruce)\
**Post date:** [December 19, 2019, 5:20pm UTC](https://community.tempest.earth/t/api-key-request/4975/1 "2019-12-19T17:20:31Z")

</div>

I’ve sent two emails to [support@weatherflow.com](mailto:support@weatherflow.com) requesting an API key in the past couple weeks. I’ve heard absolutely nothing back regarding my requests. How long do such requests typically take?

---

<div class="post-metadata">

**Author:** ![eric](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/eric/32/13553_2.png) [@eric](https://community.tempest.earth/u/eric)\
**Post date:** [December 19, 2019, 5:24pm UTC](https://community.tempest.earth/t/api-key-request/4975/2 "2019-12-19T17:24:43Z")

</div>

Hell Bruce  
At present time there are no ‘private’ api keys to my knowledge

just use the one on [this page](https://weatherflow.github.io/SmartWeather/api/)

---

<div class="post-metadata">

**Author:** ![bruce](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/bruce/32/5826_2.png) [@bruce](https://community.tempest.earth/u/bruce)\
**Post date:** [December 19, 2019, 5:26pm UTC](https://community.tempest.earth/t/api-key-request/4975/3 "2019-12-19T17:26:05Z")

</div>

That page clearly states:

> When ready to deploy an applications/integration intended for use by others (more than one user, not yourself):
> 
> - Please [contact us](mailto:support@weatherflow.com?subject=Smart%20Weather%20API%20Key%20Request) to obtain your own API key.
> - Please include a description of the app or integration you’re working on, and any other helpful information.

Is that not actually the case?

---

<div class="post-metadata">

**Author:** ![eric](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/eric/32/13553_2.png) [@eric](https://community.tempest.earth/u/eric)\
**Post date:** [December 19, 2019, 5:27pm UTC](https://community.tempest.earth/t/api-key-request/4975/4 "2019-12-19T17:27:40Z")

</div>

As said I haven’t heard of but let’s call in @WFstaff.

Can you please give a status on the api keys please ??

---

<div class="post-metadata">

**Author:** ![WFstaff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/wfstaff/32/6006_2.png) [@WFstaff](https://community.tempest.earth/u/WFstaff)\
**Post date:** [December 19, 2019, 5:36pm UTC](https://community.tempest.earth/t/api-key-request/4975/5 "2019-12-19T17:36:07Z")

</div>

Hi Bruce, we have a total of 0 tickets from this email address, sorry.

Here’s our initial messaging for an API key request…  
You can use the developer key found in the link below for testing and development.  
[https://weatherflow.github.io/SmartWeather/api/](https://weatherflow.github.io/SmartWeather/api/)

Please continue using the developer’s API key for now. It doesn’t have any restrictions on it, yet. We’ll be rolling out new developer tools soon, including a self-serve API generator. And we won’t apply any restrictions to the dev key until after giving developers plenty of time to create their own. We’ll use [https://community.tempest.earth/c/developers](https://community.tempest.earth/c/developers) for any announcements.

Do you need your own API key now? We can ask IT if so.

---

<div class="post-metadata">

**Author:** ![bruce](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/bruce/32/5826_2.png) [@bruce](https://community.tempest.earth/u/bruce)\
**Post date:** [December 19, 2019, 5:44pm UTC](https://community.tempest.earth/t/api-key-request/4975/6 "2019-12-19T17:44:01Z")

</div>

Thanks, I guess I’ll just keep using that developer key for the time being then.

> Hi Bruce, we have a total of 0 tickets from this email address, sorry.

Could you please check your spam filters? My two emails were clearly successfully delivered to Google, which is what you use:

> maillog:Dec 6 16:31:37 port postfix/smtp[29133]: 09330439E: to=[support@weatherflow.com](mailto:support@weatherflow.com), [relay=aspmx.l.google.com](http://relay=aspmx.l.google.com)[2607:f8b0:400d:c00::1a]:25, delay=0.59, delays=0.01/0.01/0.28/0.29, dsn=2.0.0, status=sent (250 2.0.0 OK 1575649897 i54si7507058qti.373 - gsmtp)
> 
> maillog:Dec 15 13:48:55 port postfix/smtp[30688]: 3AA7343A7: to=[support@weatherflow.com](mailto:support@weatherflow.com), [relay=aspmx.l.google.com](http://relay=aspmx.l.google.com)[2607:f8b0:400d:c09::1b]:25, delay=0.69, delays=0/0.01/0.21/0.47, dsn=2.0.0, status=sent (250 2.0.0 OK 1576417735 k15si8494587qtu.386 - gsmtp)

---

<div class="post-metadata">

**Author:** ![WFstaff](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/wfstaff/32/6006_2.png) [@WFstaff](https://community.tempest.earth/u/WFstaff)\
**Post date:** [December 19, 2019, 5:53pm UTC](https://community.tempest.earth/t/api-key-request/4975/7 "2019-12-19T17:53:47Z")

</div>

Thanks for checking. I checked spam messages and couldn’t find anything, sorry!

---

<div class="post-metadata">

**Author:** ![hakan.billig](https://avatars.discourse-cdn.com/v4/letter/h/8c91f0/32.png) [@hakan.billig](https://community.tempest.earth/u/hakan.billig)\
**Post date:** [December 5, 2020, 6:24am UTC](https://community.tempest.earth/t/api-key-request/4975/8 "2020-12-05T06:24:32Z")

</div>

I can not find an API key to use on the page you refer to

---

<div class="post-metadata">

**Author:** ![eric](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/eric/32/13553_2.png) [@eric](https://community.tempest.earth/u/eric)\
**Post date:** [December 5, 2020, 7:53am UTC](https://community.tempest.earth/t/api-key-request/4975/9 "2020-12-05T07:53:35Z")

</div>

A personal API can be created via the settings of the webpage and then down the page you have data autorisation, push the create token and you have it.
