Concepts
Stores and scopes
Marketplace workspaces give each seller a key, an audience and consent of its own.
This page is for marketplace workspaces. In an own brand workspace these routes answer 404 not_found. See workspace type.
A store is one seller inside a workspace. The API calls it a scope: the word scope appears in paths and fields, and these docs say store in prose.
What a store gets#
- A store key (
ktg_scope_...) or a store token that opens only that store. - An audience made of people who follow it or bought from it, with consent per store.
- A policy: a tier, a reach cap, monthly campaign quotas, a trust tier and a ramp step for new stores.
- Health: Sapagan can pause a store automatically when bounce, complaint or unsubscribe rates are high. The store can appeal.
- Blocks: the marketplace can block a store for a reason, for some days or for good. The store sees why and can appeal.
What a store credential can see#
A store sees only people with a live relationship to it, and only its own relationship. Email and phone are masked. It sees only events tagged with its own id. Anything else is 404 not_found, with the same body whether it exists or not.
A store credential cannot write consent and cannot raise its own caps.
Store tokens#
A seller portal does not hold a key per store. It exchanges the seller's own session for a short-lived store token. POST /v1/auth/scope-token is for the marketplace's backend and is not part of the public reference.
Routes#
Store routes are in the reference under Stores: reading a store, its policy, usage, audience, products, blocks, health and automatic flows. Workspace keys use the /v1/scopes/{id}/... forms. Store keys use the /v1/scope/... forms.