# Creating Openai API keys programmatically

**URL:** https://community.openai.com/t/creating-openai-api-keys-programmatically/68156
**Category:** API
**Created:** [February 20, 2023, 1:00pm UTC](https://community.openai.com/t/creating-openai-api-keys-programmatically/68156 "2023-02-20T13:00:14Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![mc1903](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/mc1903/32/723379_2.png) [@mc1903](https://community.openai.com/u/mc1903)
#### Post date: [February 20, 2023, 2:42pm UTC](https://community.openai.com/t/creating-openai-api-keys-programmatically/68156/10 "2023-02-20T14:42:14Z")

</div>

> [@ruby\_coder](#):
>
> OpenAI Terms of Usage

Fair point. Do you have any specific reference in the OpenAI Terms of Usage that forbids this; had a quick skim couldn’t see anything.

It seems reasonable to separate your user side traffic from the back end traffic, especially to protect your actual back end API key.

---

_[View the full topic](https://community.openai.com/t/creating-openai-api-keys-programmatically/68156)._