> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Link a partner storefront

> How a curator storefront links another storefront's inventory as a source, what activating it needs, and what the fixed pass-through terms mean.

A curator storefront can sell inventory that belongs to another storefront. It
links that storefront as a **linked partner source**. When a buyer brief reaches
the curator, the curator forwards it to the partner and returns the partner's
products. The curator does not copy the partner's catalog.

Linked partner sources are in a pilot. They work only for storefronts that
Apostra has enabled them for. For any other storefront, linking and activating
are refused with `FEATURE_NOT_ENABLED`.

## Link a partner

Name the seller whose inventory you want:

```json theme={null}
{ "sellerId": 9001 }
```

Send that to `save_inventory_source`. It creates a source in the `PENDING` state
and returns it. The source belongs to your own storefront: you cannot name an
owner. Linking the same partner again returns the source that already exists.

The partner seller must already have approved your storefront's account as a
buyer on their storefront. The partner does this in their own account, the same
way a seller approves any buyer. Without that approval the call answers
`NOT_FOUND`, exactly as it does for a storefront that does not exist, so a
curator cannot learn whether a storefront exists without its approval.

A pending source is not selected for buyer briefs and cannot be booked.

## Activate it

```json theme={null}
{ "id": "linked-storefront:9001", "status": "ACTIVE" }
```

Activating does two things in one call: it sets the source's terms, then turns
it on. You can also send `sellerId` and `status: "ACTIVE"` together to
link and activate at once. A source that is already active is returned
unchanged.

Activation checks the partner seller's approval again. If the partner has
withdrawn it since you linked, activation is refused, the source stays
`PENDING` and the answer says why. Ask the partner seller to approve you again,
then send the same call again.

## How a brief reaches the partner

When a buyer's brief reaches your storefront, it is forwarded to each active
linked partner. The partner shows products only under an account its buyer
holds, so your storefront first sets up an account at the partner for the
brand the buyer names and your own operator, then asks for products under that
account. The partner decides whether to open it, which is the approval you
already hold from that seller. If the partner opens no account, or the brief
names no brand, nothing is asked of that partner and the answer says so.

## The terms

The terms are fixed and you do not enter them:

| Term | Value |
| - | - |
| Pricing | Pass-through. A buyer pays the partner's price. |
| Retained share | 0%. Your storefront keeps none of the spend. |
| Supplier settlement | Outside Apostra. The partner is paid outside Apostra. |

Because nothing can be chosen, there is no separate call to set terms. They are
set when the source is activated.

## Turn it off

```json theme={null}
{ "id": "linked-storefront:9001", "status": "DISABLED" }
```

A disabled source is no longer offered for new briefs or bookings. To turn it
back on, activate it again.

## Read where it stands

`get({ "kind": "inventory_source", "id": "linked-storefront:9001" })` returns
`linkedSeller`:

| Field | Meaning |
| - | - |
| `sellerId` | The seller the source links. |
| `lifecycleStatus` | `PENDING_ACCOUNT_TERMS_AND_ROUTING`, `PENDING_TERMS_AND_ROUTING`, `ACTIVE` or `DISABLED`. |
| `accountEvidencePresent` | Whether the partner's approval of your account is current. |
| `selectable` | Whether buyer briefs reach the partner through this source now. |
| `activationRequirements` | What is still missing while the source is pending. |

`connection.nextStep` names the next action for the state the source is in.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.