---
title: "Marketplace keys"
url: https://docs.corefinity.com/guides/organisation/hosting-defaults/marketplace-keys
type: guide
last_updated: 2026-11-13
feature: magento
related:
  - https://docs.corefinity.com/api/reference/organisation/get-company-magento-keys.md
  - https://docs.corefinity.com/api/reference/organisation/update-company-magento-keys.md
  - https://docs.corefinity.com/api/reference/organisation/delete-company-magento-keys.md
  - https://docs.corefinity.com/api/reference/organisation/check-company-magento-keys.md
  - https://docs.corefinity.com/api/reference/organisation/get-own-company-magento-keys.md
  - https://docs.corefinity.com/api/reference/organisation/update-own-company-magento-keys.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_update.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_delete.md
  - https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_check.md
---
# Marketplace keys

Add your organisation's Magento Marketplace access keys so its Magento sites install and build with your own account.

## Before you start

- You are a user of the organisation that owns the sites.
- You have the public and private key from Magento Marketplace, under **My profile › Access keys**. Each is 32 characters.
- Magento Open Source installs use Corefinity's keys until you add your own. Adobe Commerce needs your own keys, from an account with an Adobe Commerce licence.

## Add your keys

1. **Open Marketplace keys**

   Go to **Organisation › Organisations**, choose your organisation, then **Marketplace keys** under **Hosting**.

   _Screenshot: The organisation page's menu with Marketplace keys ringed under Hosting, and the Magento Marketplace keys card marked Using Corefinity’s keys, with No keys yet and an Add keys button._

2. **Paste both keys**

   Choose **Add keys**. Paste the **Public key** and the **Private key**.

   _Screenshot: The Add your Marketplace keys dialog: a Public key field with a 32-character key and the line Shown later as its last four characters, a hidden Private key marked Never shown again once saved, and the buttons Cancel and Save keys._

3. **Save the keys**

   Choose **Save keys**: the keys are checked with `repo.magento.com` before they are saved. Then choose **Done**.

The keys are stored encrypted. Only the last four characters of the public key are shown again.

## Read the result

| You see                                 | It means                                                                  |
| --------------------------------------- | ------------------------------------------------------------------------- |
| **Your keys · Adobe Commerce included** | Magento Open Source and Adobe Commerce sites use your keys.               |
| **Your keys · Open Source only**        | The keys work, but their account has no Adobe Commerce licence.           |
| **Adobe Commerce unchecked**            | The keys are saved, but Adobe could not be reached. Choose **Try again**. |
| **Keys rejected**                       | `repo.magento.com` no longer accepts the keys. Choose **Replace…**.       |
| **Using Corefinity’s keys**             | The organisation has no keys of its own.                                  |

When you save, **repo.magento.com rejected these keys** means nothing was saved: check both keys against **Access keys** and try again.

## Replace, re-check or remove keys

1. **Replace or re-check**

   In **Marketplace keys**, choose **Replace…** to paste new keys. Open the card's **…** menu for **Re-check Adobe Commerce** or **Remove keys…**.

2. **Confirm a removal**

   **Remove keys…** names the Adobe Commerce sites that build with the keys. If there are any, type the organisation's name, then choose **Remove keys**.

   > **Warning:** Deployments of Adobe Commerce sites fail until new keys are added. Magento Open Source sites go back to Corefinity's keys.

## Keys for a client

An agency that manages a client's sites sets that client's keys on the client's organisation page. An agency's own keys are never used for a client's sites.

## Automate this

**API:** [Update your company's Marketplace keys](https://docs.corefinity.com/api/reference/organisation/update-own-company-magento-keys.md), scope `write`

```bash
curl -X PUT https://manage.corefinity.com/api/company/magento-keys \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "private_key": "fedcba9876543210fedcba9876543210",
    "public_key": "0123456789abcdef0123456789ab3f9a"
  }'
```

**MCP:** [`corestack_company_magento_keys_update`](https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_update.md), scope `write`

```json
{
  "name": "corestack_company_magento_keys_update",
  "arguments": {
    "public_key": "0123456789abcdef0123456789abcdef",
    "private_key": "fedcba9876543210fedcba9876543210"
  }
}
```

**Control Panel:** Organisation › Organisations › your organisation › Hosting › Marketplace keys ([https://manage.corefinity.com/go/magento](https://manage.corefinity.com/go/magento))

## Related

- [Magento 2](/guides/platforms/magento-2): See what differs for Magento 2.
- [Create a site](/guides/sites/create-and-manage/create-a-site): Add a site to a CoreCluster.
- [Application versions](/guides/sites/software-and-services/application-versions): See which release a site runs.
