Credentials and onboarding

Every platform, whatever its subscription, uses two credentials in the sandbox and in production. It calls Snapcaster with a seller’s marketplace API key, and it verifies Snapcaster’s webhooks with its own signing secret.

Send the seller’s key as a bearer token, Authorization: Bearer mp_{sellerCode}_{hex}, on every request you make for that seller. The key identifies the seller, so you do not send a separate seller id. There is no API key shared by all sellers on a platform.

When you receive a seller’s key, validate it with GET /me and store the sellerId and sellerCode it returns with the key. sellerId is the same number as data.seller_id on every webhook event for that seller, so you can route each event to its seller from the first one. The same response names your platform’s subscription in subscription: orders, inventory or both. Check it before you build, because it decides your path and which event moves your stock.

Onboard once in each environment, the sandbox first and production when you go live.

1. Email info@snapcaster.gg with the subscription you need, your webhook endpoint URL, and your technical contact’s email address. Choose your path explains the three subscriptions.
2. Snapcaster sets up your platform, registers your endpoint, and sends a 1Password share link to your technical contact. The link comes by email or over a channel you already use with Snapcaster, such as Discord.
3. Open the link when you are ready to copy its values into your own secret store. It opens only for your technical contact’s email address, and 1Password emails a verification code to that address before it shows the item.
4. Copy every value into your secret store, because the share expires after one view or 24 hours.
5. Reply to Snapcaster to confirm you received the share, but do not repeat any value.

The sandbox share holds your sandbox signing secret and the sandbox seller’s marketplace API key, login, and authenticator secret. The production share holds only your production signing secret, because each production seller generates its own key.

If the link expired or says it was already viewed, ask Snapcaster for a new one, and Snapcaster rotates the credentials it held first. Snapcaster’s emails and chat messages carry only the link, never a credential value, so never send a signing secret by email either. To change your endpoint later, email info@snapcaster.gg. One subscription for each platform covers changing your subscription.

Snapcaster provisions no seller in production. Each seller signs up through partner onboarding once Snapcaster admits it for your platform, then generates its own key in its Snapcaster dashboard and gives it to your platform to validate. Set up each seller has each step and who takes it.

Your platform has one live signing secret in each environment, so a rotation is a cutover at a time you agree with Snapcaster.

1. Email info@snapcaster.gg to ask for a new signing secret, and agree on a time for the switch.
2. Store the new secret from the 1Password share Snapcaster sends you.
3. At the agreed time, Snapcaster replaces the secret and signs every later attempt with the new one, including retries of earlier events. Switch your receiver to the new secret at the same time.

If a delivery fails verification during the switch, return non-2xx, and Snapcaster retries it signed with the new secret.

The rest of setup lives on other pages.