Go live

Production is a separate environment, so once your integration works in the sandbox, your platform, each seller, and every credential need a fresh setup there. Set up your production platform once, then each seller in order. Each step names who acts.

1. Your team emails info@snapcaster.gg to set up your production platform, following Onboard your platform. Name the same subscription you built against in the sandbox, your production webhook endpoint URL, and your technical contact’s email address. The endpoint URL must use HTTPS on a host that is reachable from the public internet.
2. Snapcaster sets up your production platform with that subscription and pins it to the API version your sandbox platform uses. It registers your production webhook endpoint and sends a new production signing secret in a 1Password share link to your technical contact.
3. Your team stores the production signing secret apart from your sandbox secret, and your receiver verifies production deliveries with it.
4. Your team points production traffic at https://api.snapcaster.ca/api/v1/marketplace.
5. Your team removes every call to the sandbox-only operations POST /sandbox/test-purchases, GET /sandbox/test-purchases/{ref}, POST /sandbox/orders/{orderId}/cancellation-requests, POST /sandbox/orders/{orderId}/change-requests, and POST /sandbox/orders/{orderId}/change-requests/{requestId}/answer, which the production API does not serve. Your team also removes the account API requests your sandbox seller setup used, because production sellers finish setup in their Snapcaster dashboard.

Complete these steps in order for each seller.

1. The seller creates a Snapcaster account and gives your team its email address. Your team emails info@snapcaster.gg with that address and your platform’s name, and Snapcaster admits the seller for your platform.
2. The seller creates its seller profile through partner onboarding at https://snapcaster.ca/sellers/onboarding/partner. The store profile step names your platform, and a seller admitted for more than one platform chooses the one this store sells through. Partner onboarding links the seller to that platform, so its webhooks reach your endpoint. A seller created through any other onboarding cannot generate a marketplace API key. A seller that already sells on Snapcaster skips steps 1 and 2. Instead, your team emails info@snapcaster.gg with its account email address and your platform’s name, and Snapcaster moves the seller onto your platform.
3. The seller enrols an authenticator app for two-factor authentication.
4. The seller generates a marketplace API key in its Snapcaster dashboard, confirms it with an authenticator code, and gives it to your platform. Snapcaster shows the key only once.
5. Your platform validates the key with GET /me on the production base URL and stores the sellerId and sellerCode it returns. Check that the returned subscription matches the one you built against in the sandbox.
6. For the first seller only, your platform sends POST /webhooks/test to production with that seller’s key and a new UUID Idempotency-Key. Confirm that your receiver verifies the signed webhook.test, the same check as Test your receiver.
7. Your platform pushes the seller’s listings with an asOf at the time you measured on-hand, then confirms them with GET /me counts and GET /listings.
8. In its Snapcaster dashboard, the seller closes every remaining requirement that GET /me lists in readiness.incompletePrerequisites. Browse readiness lists each code and who closes it. Your platform closes VACATION_DISABLED with PATCH /me and {"vacation": false}, using the marketplace API key.
9. Snapcaster reviews the seller, usually within twelve hours, and closes OPERATOR_REVIEW_APPROVED. Once GET /me reports readiness.browseEligible: true, the seller’s matched listings with stock enter browse, and counts.browsable counts them.

Production has no test purchase, so until a real buyer places the first order, the test event in step 6 is what tells you your production receiver works.

These terms come from section 10 of the Snapcaster Terms of Service, which each seller accepts as the Seller Terms.

• Commission plus processing fee. Before payout, Snapcaster deducts a commission of 5% of the merchandise price, capped at $50 per item, plus a processing fee of 2.9% + $0.30 on the order total including shipping. It also withholds the commission tax at the seller’s provincial rate, and any sales tax Snapcaster collected as a marketplace facilitator.
• Purchase fee. Buyers pay a separate purchase fee of 3.5% of the card subtotal at checkout. What the buyer gets back says when a cancellation or refund returns it.
• Payouts. Each order pays out on its own to the seller’s Stripe account once it is marked shipped and its hold window has passed.
• Hold window. Snapcaster sets the hold window per seller, and keeps it longer for a new seller until it has a track record. The seller sees its current window in its Snapcaster dashboard.
• Shipping standard. Sellers ship within 3 business days of the order, which is the dispatch.deadline_at your platform reads.

Sandbox guarantees lists what holds in the sandbox, and Rate limits gives the production listing rate.

Production has no formal uptime or support response-time commitment yet. Email info@snapcaster.gg about an incident. For a request that keeps failing, Retries says what to include.

These docs leave two things open. If your launch plan depends on either, email info@snapcaster.gg and ask before you launch.

• The exact per-seller listing item ceiling, if you need more than the floor Rate limits gives.
• A firm turnaround for Snapcaster’s review of a seller, beyond the usual twelve hours.