Authorization: Bearer $SCOPE3_API_KEY. The storefront is resolved from your API key’s seller customer context — there is no customerId path parameter. The one exception is Get join context, which is public and unauthenticated so the signup page can theme itself before the buyer has an account.
Key concepts
- Slug. Every link has a URL-safe
slug(lowercase letters, numbers, hyphens). Omit it on creation and it is derived from the storefront name. The buyer visitsjoinPath(/join/{slug}); your UI or agent prepends its own origin. - Approval policy. Set at mint time and fixed for the life of the link:
auto_approve— signups becomeactivesponsored buyers immediately.manual_approve(default) — signups landpendinguntil you approve them.invite_only— admits signups the same way asmanual_approve(they landpending); reserved for future invite-gated entry.closed— refuses new signups;get-join-contextreports a closed link as invalid.
- Caps and expiry.
maxUsescaps total successful signups (omit for unlimited);expiresAtis an ISO-8601 expiry (omit for a link that never expires).usescounts successful signups so far. - Posture. Sponsored buyers are
prepayday-one; theposturefield future-proofs for credit terms. - Disable, don’t delete. Disabling a link soft-revokes it (
active: false,revokedAtset). Buyers who already joined keep their accounts — disabling only stops new signups.
A join link only controls entry. After a buyer joins, their ability to transact is governed by their sponsored-buyer
status, which you control independently. See Sponsored buyers.Task reference
Create join link
Mint a link for one of your storefronts
List join links
Every active link your organization owns
Disable join link
Soft-revoke a link to stop new signups
Get join context
Public brand-safe lookup for the signup page
Related
Sponsored buyers
Manage the buyers who joined
All join-link tasks
Every operation in one place
Storefront onboarding
End-to-end seller setup
Errors
Shared error contract