> For the complete documentation index, see [llms.txt](https://docs.flashback.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flashback.tech/support-reference/platform-api-reference/ai-apis/ai-api-keys/post__repo_-repoid-_ai_apikey.md).

# post\_\_repo\_{repoId}\_ai\_apikey

{% hint style="info" %}
This API endpoint is currently available only in the TEST environment. It is not yet available in production.
{% endhint %}

`POST /repo/{repoId}/ai/apikey`

*Create Repository AI API Key*

Create a new AI-specific API key for a repository. These keys are used to access AI-powered features and services for the repository, providing secure authentication for AI operations.

**Key Features:**

* Automatically generates unique API key and secret pairs
* Keys are specific to a single repository
* Supports different AI provider types (OPENAI, GOOGLE, ANTHROPIC, AWS, OTHER)
* Encrypted storage of secrets
* Repository-scoped access control

**Important Notes:**

* The secret is only returned once during creation - store it securely
* Users must have access to the repository to create API keys
* Keys are soft-deleted (marked as deleted but not physically removed)
* Each key is associated with a specific AI provider type

**Security:**

* Secrets are encrypted before storage using industry-standard encryption
* API key and secret are generated using cryptographically secure methods
* Keys respect repository access controls
* System events are logged for audit trails

#### TypeScript Client Library

```typescript
public createRepoAiApiKey = async (repoId: string, data: CreateRepoAiApiKeyRequest): Promise<CreateRepoAiApiKeyResponse> => {
  return this.makeRequest<CreateRepoAiApiKeyResponse>(`repo/${repoId}/ai/apikey`, 'POST', data);
};
```

#### Code Samples

{% tabs %}
{% tab title="Shell" %}

```shell
# You can also use wget
curl -X POST https://backend.flashback.tech/repo/{repoId}/ai/apikey \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer {access-token}'
```

{% endtab %}

{% tab title="HTTP" %}

```http
POST https://backend.flashback.tech/repo/{repoId}/ai/apikey HTTP/1.1
Host: backend.flashback.tech
Content-Type: application/json
Accept: application/json
```

{% endtab %}

{% tab title="JavaScript" %}

```javascript
const inputBody = '{
  "name": "Production AI Key",
  "aiType": "OPENAI"
}';
const headers = {
  'Content-Type':'application/json',
  'Accept':'application/json',
  'Authorization':'Bearer {access-token}'
};

fetch('https://backend.flashback.tech/repo/{repoId}/ai/apikey',
{
  method: 'POST',
  body: inputBody,
  headers: headers
})
.then(function(res) {
    return res.json();
}).then(function(body) {
    console.log(body);
});
```

{% endtab %}

{% tab title="Ruby" %}

```ruby
require 'rest-client'
require 'json'

headers = {
  'Content-Type' => 'application/json',
  'Accept' => 'application/json',
  'Authorization' => 'Bearer {access-token}'
}

result = RestClient.post 'https://backend.flashback.tech/repo/{repoId}/ai/apikey',
  params: {
  }, headers: headers

p JSON.parse(result)
```

{% endtab %}

{% tab title="Python" %}

```python
import requests
headers = {
  'Content-Type': 'application/json',
  'Accept': 'application/json',
  'Authorization': 'Bearer {access-token}'
}

r = requests.post('https://backend.flashback.tech/repo/{repoId}/ai/apikey', headers = headers)

print(r.json())
```

{% endtab %}

{% tab title="PHP" %}

```php
<?php

require 'vendor/autoload.php';

$headers = array(
    'Content-Type' => 'application/json',
    'Accept' => 'application/json',
    'Authorization' => 'Bearer {access-token}',
);

$client = new \GuzzleHttp\Client();

// Define array of request body.
$request_body = array();

try {
    $response = $client->request('POST','https://backend.flashback.tech/repo/{repoId}/ai/apikey', array(
        'headers' => $headers,
        'json' => $request_body,
       )
    );
    print_r($response->getBody()->getContents());
 }
 catch (\GuzzleHttp\Exception\BadResponseException $e) {
    // handle exception or api errors.
    print_r($e->getMessage());
 }

 // ...
```

{% endtab %}

{% tab title="Java" %}

```java
URL obj = new URL("https://backend.flashback.tech/repo/{repoId}/ai/apikey");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("POST");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
    new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
    response.append(inputLine);
}
in.close();
System.out.println(response.toString());
```

{% endtab %}

{% tab title="Go" %}

```go
package main

import (
       "bytes"
       "net/http"
)

func main() {

    headers := map[string][]string{
        "Content-Type": []string{"application/json"},
        "Accept": []string{"application/json"},
        "Authorization": []string{"Bearer {access-token}"},
    }

    data := bytes.NewBuffer([]byte{jsonReq})
    req, err := http.NewRequest("POST", "https://backend.flashback.tech/repo/{repoId}/ai/apikey", data)
    req.Header = headers

    client := &http.Client{}
    resp, err := client.Do(req)
    // ...
}
```

{% endtab %}
{% endtabs %}

> Body parameter

```json
{
  "name": "Production AI Key",
  "aiType": "OPENAI"
}
```

#### Parameters <a href="#post__repo_-repoid-_ai_apikey-parameters" id="post__repo_-repoid-_ai_apikey-parameters"></a>

| Name     | In   | Type   | Required | Description                         |
| -------- | ---- | ------ | -------- | ----------------------------------- |
| repoId   | path | string | true     | Unique identifier of the repository |
| body     | body | object | true     | none                                |
| » name   | body | string | true     | Human-readable name for the API key |
| » aiType | body | string | true     | Type of AI provider this key is for |

**Enumerated Values**

| Parameter | Value     |
| --------- | --------- |
| » aiType  | OPENAI    |
| » aiType  | GOOGLE    |
| » aiType  | ANTHROPIC |
| » aiType  | AWS       |
| » aiType  | OTHER     |

> Example responses

> 201 Response

```json
{
  "success": true,
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "key": "FB_AI_abc123def456",
  "secret": "secret_xyz789abc123def456"
}
```

#### Responses <a href="#post__repo_-repoid-_ai_apikey-responses" id="post__repo_-repoid-_ai_apikey-responses"></a>

| Status | Meaning                                                                    | Description                  | Schema |
| ------ | -------------------------------------------------------------------------- | ---------------------------- | ------ |
| 201    | [Created](https://tools.ietf.org/html/rfc7231#section-6.3.2)               | API key created successfully | Inline |
| 403    | [Forbidden](https://tools.ietf.org/html/rfc7231#section-6.5.3)             | Insufficient permissions     | Inline |
| 500    | [Internal Server Error](https://tools.ietf.org/html/rfc7231#section-6.6.1) | Failed to create API key     | Inline |

#### Response Schema <a href="#post__repo_-repoid-_ai_apikey-responseschema" id="post__repo_-repoid-_ai_apikey-responseschema"></a>

Status Code **201**

| Name      | Type    | Required | Restrictions | Description                                      |
| --------- | ------- | -------- | ------------ | ------------------------------------------------ |
| » success | boolean | false    | none         | Operation success status                         |
| » id      | string  | false    | none         | Unique identifier for the created API key        |
| » key     | string  | false    | none         | The access key (store securely)                  |
| » secret  | string  | false    | none         | The secret key (store securely, only shown once) |

**IMPORTANT:** The `secret` is only returned during creation. Store it securely as it cannot be retrieved again.

Status Code **403**

| Name      | Type    | Required | Restrictions | Description   |
| --------- | ------- | -------- | ------------ | ------------- |
| » success | boolean | false    | none         | none          |
| » id      | string  | false    | none         | none          |
| » key     | string  | false    | none         | none          |
| » secret  | string  | false    | none         | none          |
| » message | string  | false    | none         | Error message |

Status Code **500**

| Name      | Type    | Required | Restrictions | Description   |
| --------- | ------- | -------- | ------------ | ------------- |
| » success | boolean | false    | none         | none          |
| » id      | string  | false    | none         | none          |
| » key     | string  | false    | none         | none          |
| » secret  | string  | false    | none         | none          |
| » message | string  | false    | none         | Error message |

To perform this operation, you must be authenticated by means of one of the following methods: BearerAuth


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flashback.tech/support-reference/platform-api-reference/ai-apis/ai-api-keys/post__repo_-repoid-_ai_apikey.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.