Sales channels

Cypress distributes one listing to several selling surfaces. Each channel has its own audience and its own commission scheme; your org holds a grant per channel, and the API validates channels[] against those grants.

The channels

• MARKETPLACE (default) — the public Cypress marketplace. Broadest reach; buyers negotiate through offers.
• STOREFRONT — your org's branded storefront. Can carry inventory withheld from the public marketplace (a listing with channels: ["STOREFRONT"] is not publicly browsable).
• DIRECT_LINK — a shareable per-vehicle link, auto-provisioned at launch. Its URL comes back in listing responses and in the LISTINGS.ACTIVATED event — hand it to a buyer directly.

Curated promotions exist as a fourth surface and can join the API when you need them.

In practice

• Broad liquidation — ["MARKETPLACE"]: maximum eyes, offer-driven price discovery. The default for de-fleeting and repossessions.
• Protecting a retail brand — ["STOREFRONT"]: a dealer group sells aging units to its own wholesale audience without the cars appearing on the public marketplace next to its retail listings.
• A negotiated single buyer — ["MARKETPLACE", "DIRECT_LINK"]: the link goes to the buyer you're already talking to; if they stall, the marketplace keeps working in the background. The link URL rides in every listing response and in LISTINGS.ACTIVATED.

Selecting channels via the API

{ "channels": ["MARKETPLACE", "DIRECT_LINK"], "buyNowPrice": 22500 }

One listing, one price, several surfaces (a deliberate divergence from Manheim's one-offering-per-channel model). Requesting a channel your org has no grant for answers 422 — grants are managed by Cypress on your account.

A Cypress manager's automation can set a vehicle's channels too, with the same rule and the same grants (the Set sales channels automation action, documented in Automations). When it changes an open API listing's channels, your LISTINGS.UPDATED webhook fires as for a push.