Partner Integration Walkthrough

Agree the commercial model before creating orders

Obtain an approved developer-partner relationship, assigned products, fulfillment rules, and the needed API scopes. A reseller collecting payment externally remains the seller for that payment and covers its own processing and tax responsibilities. A referral paid through SoundSync checkout is a different, managed-sale model.

Use the scoped partner key, not a developer dashboard token or plugin credential. Map the reseller SKU to an assigned product and choose a stable external order reference. Keep API secrets and customer data out of logs and public examples.

Send one order and replay the identical request

Follow the external-order API example with customer_email, purchased_at, the external reference, item SKU/quantity, and the required amounts. POST /api/partner/v1/orders requires Idempotency-Key. Reuse the same key only for the identical request body; do not generate a fresh key to hide an uncertain outcome.

Inspect the returned order, relevant fulfilled lines, and any serial or entitlement result. Replaying the same request should identify the same work rather than issue duplicate access. For mixed carts and refunds, preserve each original line identity and leave unassigned products alone. An imported payment amount is not collected SoundSync money or an automatic payout.

Test safely

Use permitted test identities and the intended environment. Inspect allowed and rejected outcomes. Keep private customer data, serials, credentials, payment details, and verification links out of published examples.