---
title: "Get the client key of a Connect addon"
method: GET
path: "/addon/{addon_key}/client-key"
tags: ["Addon"]
---

# Get the client key of a Connect addon

`GET /addon/{addon_key}/client-key`

Get the client key of the Connect addon associated with a Forge app install via forgeAppId linkage.

This endpoint is part of the Connect -> Forge migration tooling. It is intended to be used by a Forge app
using `asApp().requestBitbucket()` only.
Prerequisite: app developer needs to register the linkage between their Connect and Forge app by setting
`forgeAppId` in the Connect addon descriptor to `app.id` from Forge app manifest, then update the installations.
If the request came from an installation of a registered Forge app, the client key of the linked Connect addon
installed in the same workspace will be returned.

```
api.asApp().requestBitbucket(route`/2.0/addon/{addon-key}/client-key`)
```

## Response `200`

The client key of the Connect addon linked to the Forge app installation where the request was made

## Other responses

- `401` — Invalid authentication.
- `403` — Improper authorization.
- `404` — The Connect addon or the Forge app does not exist.

---

[API](https://skmtc.net/bitbucket/apis/bitbucket-api.md) · [All operations](https://skmtc.net/bitbucket/apis/bitbucket-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bitbucket/bitbucket-api/revisions/4ec8bd2515c5/schema)