Guide
Serial Generation and Distribution
Known serial batches, imports, exports, external claims, and customer proof.
Create known serials for the intended product
The developer tools include serial generation for permitted manual, partner, promotion, and verification workflows. Use the product and batch scope you intend to distribute; generated serials are sensitive access material.
A serial can remain available, be assigned/claimed, activated, suspended, or revoked according to its access policy. A serial inventory entry and an activated device are not the same record.
SoundSync
Customer tools
SoundSync
Prepare a batch
-
Confirm product and rights
Select a saved product you are permitted to manage and the agreed distribution model.
-
Generate or import
Use the supported serial tool and CSV format. Review sample/import requirements and billing readiness.
-
Review inventory
Inspect available/status filters and group/batch data before assigning or exporting.
-
Distribute privately
Send only the authorized serials to the intended customer or approved partner. Never publish a complete serial list.
-
Test owner proof
Exercise an unclaimed serial, an existing owner, verification, device activation, and a revoked serial with test identities.
-
Reconcile claims
Review external-redemption usage and customer/device state separately.
External access and billing
Qualifying free or off-portal serial claims can count as external redemptions. Normal subsequent license validation, activation, or reactivation is not automatically a new external redemption. External reseller sales keep their own seller/payment responsibilities.
Legacy wrapper/validation tools are a separate preview/older-client path. Their existence is not an assisted migration service or proof that licenses from another provider can be imported with preserved access.
Customer identity in redeemed-serial imports
Redeemed-serial imports, through the CSV upload or legacy JSON route, reuse the existing customer identity matched by normalized email without replacing its shared name, verification, account status or marketing preferences. A new identity is created only as part of a successful imported serial row. The serial can retain its developer-specific imported name snapshot; that snapshot is not a shared account-profile edit.
Unknown or unowned products, invalid required input and duplicate serials are skipped. A duplicate race or failed serial insert rolls back any customer created for that row. Earlier successful rows can remain imported if a later row fails; review the result and retry deliberately. A serial import is not a paid checkout, inbox verification, login transfer or permission to bypass an unsubscribe.
Use the current serial import tools
Use the serial import tools in the developer dashboard or their documented current API routes. The retired /api/data/import compatibility endpoint returns 410 LEGACY_IMPORT_RETIRED and does not read uploaded files or modify serials. Current imports retain their existing permission, product-ownership and duplicate-handling checks.
Retired serial read and export views
The old /api/serials list, available, redeemed, export, serials, transactions, customers-list and resellers views return HTTP 410 with LEGACY_SERIAL_VIEW_RETIRED. Use /api/developer/serials and its export route, /api/developer/customers, /api/developer/purchases or the current Partner Hub APIs instead. The retirement response identifies the replacement; old filters and response formats are not carried forward.
Current generation, customer serial redemption, authorized downloads and guarded serial actions remain available. No serial, customer, order or purchase history is deleted by retiring these views.
