Skip to content
SoundSyncAudio software platform

Changelog

SoundSync Developer Platform Changelog

Current documentation review and preserved historical product release entries.

2026-11-17: website integrations, external licensing and clearer operational updates

Custom websites can connect verified account flows, managed checkout, customer library and private delivery without replacing their design or host. Framework starters and separate FastSpring/Gumroad/WooCommerce checkout choices now have focused guides. The API reference includes website settings, package download, provider configuration, authenticated events and checkout confirmation.

The developer inbox separates active Notices from recent Activity with affected items and retry/resolution guidance. Campaign drafts retain valid content when an optional audience count times out. Delivery-failure guidance distinguishes verified recoverable provider problems from protected customer choices. No pricing rates, team roles or financial execution flags changed.

Account references now include the older shared-account URL aliases and personal saved-card endpoints, with their store-only session restrictions. Profile/password response fields identify when store sign-in is required again. Security reads no longer turn a failed session-count query into a confirmed zero. Successful security changes remain distinguishable from a failed status refresh, with one-time recovery codes preserved.

Verified free product acquisitions can enter supported Growth Flows when deliberately enabled. Purchase-reward programs retain paid-only proof unless the flow explicitly admits free access and the program allows it. Recipient restrictions, verified popup choices and stable reward identity stay protected; free rewards do not fabricate paid orders. The guide separates acquisition-triggered flows from product-update audience eligibility and deliberate historical enrollment.

2026-11-17: offline authorization and payout export clarity

Licensing API instructions now distinguish bounded offline leases from explicit permanent-device product/content grants throughout the generated reference. The package upgrade process and Access grace behavior are unchanged.

Anonymous legacy web redemption now returns a retired response and directs customers to signed-in serial redemption. Current customer-library and native licensing paths are unchanged. Privacy and audience guidance explains automatic enrollment without claiming that it establishes sending permission everywhere.

Payout-history export guidance includes all 28 columns, fee/FX units and reconciliation states. An FX record without a valid expiry is reported as unavailable instead of quoted. This corrects a reporting label without changing amounts, fee policy, transfer execution or financial configuration.

2026-11-16: licensing, Partner Hub and payout compatibility references

The licensing reference now maps active unversioned calls, distinguishes ping from authentication and explains emailed verification HTML and compact HISE transport. Product credential docs distinguish retired developer-wide creation/reveal from actor-owned historical cleanup.

Partner Hub docs separate always-disabled order/payable-statement writes from capability-gated key creation/rotation and available key revocation. Relationship aliases retain their original scope and request semantics. Payout docs include the complete shared-router alias map, owner-only setup and report/preview boundaries. The email-marketing directory now includes the remaining shared-router aliases without creating another queue or allowance. This is a documentation update, not a change to permissions, fees, package behavior or automatic payments.

2026-11-16: workspace sessions, developer notices and funding retries

The developer header now gathers permission-filtered billing, sending and product issues. Browser-local read markers do not dismiss active issues; unavailable sources remain distinct from an empty healthy result. The notification read, response fields and account-only workspace warning are documented.

Account session discovery can return read-only developer workspace context without provisioning membership. Team troubleshooting explains choosing the intended account, inactive access and first-time setup. Dashboard compatibility aliases retain the canonical handlers and permissions.

Growth Flow funding holds preserve their planned dates and use a separate automatic-retry deadline. Recipient references include sendHoldCode and nextRetryAt, separate from uncertain-delivery review. Pricing, financial controls and automatic-transfer settings are unchanged.

2026-11-15: activity access and payout completeness

The combined activity feed applies team product assignments to records and counts. Customer, serial, order and refund details retain their own permissions, including when searching activity. Workspace-wide revenue aliases follow the same all-products rule as the main reports.

Payout reporting keeps incomplete amounts pending instead of treating them as zero. The current provider and explanation take priority over an older prepared quote. Expansion permissions remain limited to expansion and product-relationship actions.

2026-11-15: product access and partner serial safeguards

Customer product-access references now document suspend, restore and revoke with their existing workspace and entitlement permissions. Restore does not clear a serial hard-revocation flag. Expansion references distinguish permitted team reads from edits without an outdated owner-only scope.

External partner-order serial generation uses cryptographic randomness by default, matching the protection already used for generated serial pools. Existing serial codes, original sale records, financial controls and offline grants are unchanged.

2026-11-15: commercial pricing and connected reporting

Full Store uses a 3% SoundSync sales fee with a $20 sales-fee minimum. Marketing includes 1,000 emails per Eastern month, then $0.50 per started 1,000 block. Actual checkout processing is billed separately to developers; earlier records retain their recorded policy.

Customer, serial and purchase exports include all filtered records with download progress and distinct purchase identities. Bundle galleries follow current eligible included products. Marketing adds optional owner-set budgets and estimated campaign costs, with separate billing and uncertain-delivery holds.

Payout forecasts distinguish calculation completeness from payment readiness. The breakdown shows shared monthly free usage and in-period paid units, with payout-provider fees among expenses before the final total.

The upcoming payout summary and older unpaid periods have distinct scopes. Earlier unpaid earnings retain their original period; API references explain total owed, held earnings and unresolved historical sources.

External reseller estimates keep agreed shares separate from SoundSync checkout fees and preserve recorded allocations. Purchase receipts distinguish the original developer allocation from later account charges. Service-agreement API identifiers preserve decimal strings without numeric precision loss.

2026-11-13: service choices, Eastern accounting and purchase rewards

Full Store, Licensing + Hosting and Licensing now separate managed commerce from external checkout. Owner-confirmed service pricing, production activation, storage allowances and once-monthly billing are documented together.

Current accounting uses Eastern calendar months and assigned half-month sales periods. PayPal Payouts approval is confirmed, with independent inbox verification and provider eligibility checks. Payout loading preserves errors instead of presenting a failed balance request as zero.

Cross-sell flows can create and reuse purchase-reward programs. The promotion workspace supports discount editing and removal while retaining history, cart links resolve eligible published hidden products, and Plugin Notices review can enable required delivery channels without changing licensing.

2026-11-13: multi-product cross-sells and editable email headers

Cross-sell flows support multiple trigger products, matching owned-product names and one sequence per qualifying paid order. Campaign and Growth Flow email headers can be edited or removed while preserving their saved primary and reward designs.

2026-11-12: complete catalogs, bundle galleries and direct product links

Hosted and embedded catalogs traverse all eligible product pages. Bundle artwork stays independent from its complete gallery. Published hidden products support direct-link viewing and eligible website checkout while remaining absent from discovery; disabling checkout or returning to draft stops new website purchases. These controls do not revoke existing ownership.

2026-11-12: expanded API access and network-safety review

Related-product management and readiness reports now follow selected-workspace permissions. Existing legacy bundle edits and recurring-revenue reports use their corresponding scope and analytics checks. Older branding-management and analytics-report shortcuts are retired with current-tool guidance; public brand lookup and event collection remain available.

Webhook tests and compatibility remote imports pin public destination addresses and reject private-network targets. Webhook testing does not follow redirects with its secret and limits response previews. Compatibility downloads return clear invalid-proof and malformed-index errors. Existing financial flags, customer rights and offline policies are unchanged.

2026-11-12: offer collection and payout setup references

Purchase-option references clarify draft versus publication requirements, explicit retirement, recurring interval aliases and eligible protected-content collections. Payout setup documents confirmation, verification states and superseded email requests. Native and HTTP guides distinguish pending deactivation proof from confirmed server device release. Marketplace publishing guidance explains automatic relevant-store marketing enrollment and protected suppressions. These are documentation corrections, not changes to payment execution or access policy.

Unused legacy /api/customers and /api/transactions handlers, plus the old /api/me and /api/redeem/me serial-token library views, are retired with explicit 410 responses and current-API guidance. Current dashboard customer and purchase reports, imports, exports, serial redemption and licensed access are unchanged. Account-only library and entitlement-delivery references now identify the required current customer-account session rather than a legacy serial/download token.

Product and AI authoring now checks workspace/product permissions before work begins. Public asset uploads carry their authoring context and are authorized before file buffering. Three multipart asset endpoints are documented. Unused buffered uploads, old internal domain registration and legacy serial read/export views are retired with current-workflow guidance; existing serial generation, redemption, downloads and financial flags remain unchanged.

2026-11-11: protected-download account checks and clearer API examples

New native protected catalogs and download links check a linked customer account for SoundSync-wide suspension. Store restrictions remain local to that store, and issued signed offline grants and Access grace are unchanged.

Protected-delivery references distinguish customer-account sessions from native device proof. Upload-job identifiers, unpublished-release fields and offer-retirement responses match the implementation. Search includes alternative response fields, and privacy guides use consistent enrollment and suppression guidance.

Renewal guides and Terms distinguish older initial-payment promotions from the accepted schedules of versioned purchase-option deals, including locked versus supported current-list prices. Growth Flow references distinguish a new job, an existing pending job and an empty audience. Payout reporting describes fee components and reconciliation fields, and search includes fields inside array-shaped responses.

2026-11-10: purchase options, protected banks and payout detail

Products can offer one-time and recurring choices with versioned terms, price schedules and explicit collection rules. JUCE 0.9.3 keeps same-product ownership separate from software compatibility, supports independent protected-bank permissions and retains explicit permanent-device grants alongside bounded Access grace. Installed plugins need a rebuilt release to use the update.

This release added guides for private protected-archive publication, before-purchase pages and Product Marketing, historical Growth Flow eligibility, invitation continuation and payout setup. Its pricing guidance distinguished the discounted paid-cart floor from individual gift lines. Checkout-processing coverage and pending PayPal sending approval described the policy and approval state at that time, not the current service. Later entries and the current Pricing and Payout guides document the new developer-paid processing policy and approved PayPal Payouts.

Receipts retain saved promotion, coupon and BOGO details. Partner product choices distinguish native activation serials from library redemption codes. API references include the new authoring, catalog, delivery, setup and preview operations; operation-level source review is not a claim that every endpoint has production coverage.

November 5, 2026: booking and integration reference corrections

Retired the older CSV import path while retaining current serial imports. Demo booking now checks the offered appointment schedule and separates confirmed bookings from notification-record errors.

Partner guides distinguish custom fulfillment activation from approved WooCommerce, affiliate and collaborator paths. The manual-issue reference includes its test default and returned access fields. Documentation navigation, search terms and canonical links have been corrected. No financial flags or commercial policies are changed.

November 5, 2026: integration examples and demo privacy

Account security reports the saved personal account role without changing workspace permissions. The API reference distinguishes shared-account security details from store-only status.

Corrected the Plugin Notices request example and JUCE example instructions for signed Access grace. Demo pages now distinguish the two HISE paths, the JUCE package and custom HTTP integration. Privacy guidance explains existing booking information, calendar invitations and meeting links; commercial terms and marketing enrollment are unchanged.

November 5, 2026: customer access and contact consistency

SoundSync-wide customer suspension now blocks library and download authorization with existing sessions. Store restrictions remain local to the relevant developer.

Customer and developer contact corrections stay linked to the appropriate marketing contact and supported current records. Later marketing activity and imports preserve separate store details. Historical invoices, sent messages, ownership and commercial terms are unchanged.

November 5, 2026: campaign history and account guidance

Campaign-history exclusions retain known customer identity after a contact email correction. Feature categories now support keyboard navigation with linked tabs and panels, and navigation menus return focus when dismissed.

Account guides distinguish ordinary verification from verified popup account setup, and immediate customer email edits from verified platform changes. No payment, refund, payout, retention or automatic marketing-enrollment policy is changed by this documentation update.

November 4, 2026: launch, messaging and account guides

Added Plugin Notices and JUCE companion integration, reviewed product release scheduling, Meta measurement and partner workspace/statement references. Expanded ownership-driven Growth Flows, popup rewards, product-type compatibility, artwork fallback and support-delivery guidance.

Customer contact and credential guidance now distinguishes one developer storefront from shared SoundSync identity. Marketing pages describe automatic purchase/signup enrollment while preserving saved restrictions. API references include the new delivery, authoring, statement, measurement, release and device operations. Existing commercial policies and licensing upgrade instructions remain in force.

October 24: product cart links and safer serial imports

Email campaigns can create a custom product cart link or insert its editable email button. The storefront preserves existing items and recalculates the offer at checkout; the guides cover selection limits, unavailable products and embedded routing.

Redeemed-serial CSV and legacy JSON imports preserve existing shared customer profiles and roll back new customer creation when a serial is skipped by a duplicate race or fails to insert. JSON serial history commits with its transaction record. Existing product, reseller, permission and billing boundaries are unchanged.

Deactivation examples and request schemas now require the appropriate machine proof. Current licensing contract notes use the maintained JUCE and HISE version labels without repeating the same explanation. Older dated release entries remain unchanged.

October 23: ownership gifts and financial reporting references

Timed manual keep-products grants permanently include the products present at grant time without collecting payment. The guides distinguish these gifts from lifetime access, ordinary trials and ownership earned through paid invoices.

The API reference now displays complete field contracts on the newer account, grant, readiness and dashboard cards, and documents payout history, CSV exports, transfer/bank status, journal previews and recovery reports with their actual filter limits. Customer-onboarding metadata points to its customer-facing SoundSync host.

Current JUCE instructions follow 0.9.3, including activation feedback and protected Windows recovery. Existing offline-grace and deactivation safeguards remain in force. Earlier dated entries below retain their original release versions.

October 23: cart tiers, catalog selections and complete setup references

Promotions now include tiered cart discounts and automatic multi-product offers. Catalog selection supports confirmed product actions across pages and filters, with individual results and protected deletion.

Marketplace guides explain uploaded-source selection, placement-compatible core artwork and the ordered homepage sections response. The API reference adds account onboarding, Partner Hub reporting and management, product promo kits and the reseller portal, including operation-specific availability.

Signup and login navigation opens the current public pages, documentation and policies. About and account setup entry pages share the current website navigation and SoundSync canonical URLs. Existing licensing, offline grace, deactivation, legal and financial policies are unchanged.

October 22: customer-session safeguards and reporting reference updates

Customer account requests now fail closed when session verification is unavailable, with a safe retryable response instead of private access. Revoked sessions remain rejected and service recovery restores valid-session verification.

Campaign references document recorded delivery evidence, source coverage, action conflicts and operation-specific permissions. Subscription guides explain the existing billing-interval safeguard and normalized settings behavior; domain API cards identify workspace-wide access. Earlier package, login, claim and domain release notes remain below.

October 22: diagnostic permissions and subscription recovery guidance

Product connection diagnostics separate integration access from customer and serial permissions. The editable developer billing portal requires billing management access while read-only reports and downloads remain available to billing viewers.

The API reference includes the private product catalog, in-memory marketplace artwork previews, billing CSV downloads and Partner Hub relationship management. Customer-history guides distinguish access-only records and retained-access manual grants from payments.

Rental recovery guidance separates license suspension from continuing subscription billing, explains outstanding-payment reconciliation and distinguishes keep-your-products ownership. The local-storage and credential-lifecycle guides identify the current JUCE 0.7.2 package; existing offline grace and deactivation guidance is retained.

October 22: native account login, claim recovery and provider reporting

JUCE 0.7.2 and HISE Native C++ 0.5.2 add customer two-factor continuation, private in-memory challenges and corrected serial-claim request/finalization. Pending claim context survives restart and temporary retry failures. Regenerate packages, rebuild and distribute existing plugins. This entry does not claim new Apple or full HISE/DAW runtime testing.

Provider readiness now refreshes bounded cached observations, separates transactional/marketing blockers and rejects missing/expired tracking certificates. Supported marketing can disable unsafe tracking only through an enforceable provider capability. Reporting separates pending, retrying, stale and unavailable history while preserving known events, prior snapshots and financial attribution.

Documentation now covers the complete customer-login conversation, claim delivery/restart errors, DNS cooldown/setup-change recovery, purpose-specific sender readiness and provider-history fields. Authentication search uses its canonical public reference. Earlier dated entries remain historical.

October 22: JUCE signed offline grace

JUCE 0.7.1 adds signed offline access using the saved product Access grace period, up to 90 days. Product/device-bound grants preserve expiry across restart and cannot be extended by editing cached dates. The processor enforces expiry with the editor closed. Regenerate packages and rebuild existing plugins; earlier binaries retain their original behavior.

October 21: activity privacy, HISE grace and telemetry

HISE 0.5.1 removes unlimited cached-access paths and enforces the selected Access grace period. Activity records follow their individual permissions, marketplace counters no longer require manual-test history for published products, and the telemetry API includes request/response contracts. JUCE package and startup behavior are unchanged in this release.

October 20: campaign access and account-session safeguards

Campaign actions follow marketing permissions and complete product assignments, including AI product/deal context. Workspace-wide contact and sender writes require all-products marketing access. Recovery-code use is atomic, password changes revoke other sessions in the same transaction, and a failed server sign-out returns an availability error.

Added complete references for product promo codes, manual grants, account/product/storefront readiness and payout-status refresh. Canonical authentication guidance includes session-store availability errors. Payout guidance separates schedule, dedicated-account custody and setup approval.

October 20: API references and access safeguards

Added references for sending domains and sender profiles, review imports, product dashboards, revenue reporting and activity. Review CSV imports use column mapping, a preview and separate confirmation before saving pending reviews. The documentation sidebar includes the newer website, operational AI and workflow API guides.

Account session-store failures return an availability error instead of permitting unverified access. Product dashboards filter their optional information by the existing role permissions. Rent-to-own cancellation records pending provider confirmation and supports retrying the cancellation without repeating its local access changes; new live rent-to-own checkout remains unavailable.

October 17, 2026 information update

The public guides now cover catalog importing, private resumable uploads, Brand Manager section saves, Website Builder menus and history, campaign and growth-flow recovery, subscription ownership models and payment recovery, customer account history, automatic marketplace artwork, and HISE package-management calls.

Legal and trust information explains purchase-based marketing enrollment, protected unsubscribe choices, source rights and retention, email providers, and the shared twice-monthly developer, affiliate, and collaborator payout schedule. Existing package integration instructions and managed-checkout fee policies remain in place.

October 5, 2026 documentation update

Updated JUCE 0.7.0 guidance covers processor-owned enforcement, editor attachment, serial and account activation, online startup renewal, and immediate local deactivation. New references cover whole-product checkout refunds, original affiliate/collaborator share recovery, program agreements and live consent, growth-flow operations, and versioned subscription bundle billing.

Commercial guidance distinguishes SoundSync-managed processing from external reseller collections and explains the dedicated payout account. Keep-your-products documentation separates paid-invoice ownership from recurring access and unpaid trials. Earlier dated entries remain historical.

October 2, 2026 content review

Guidance now reflects JUCE 0.6.0 processor-owned online licensing, separate HISEScript/native installation, WooCommerce fulfillment, custom-domain GA4, current promotions, product media/files, customer operations, and marketing settings. Older dated entries below are retained as historical release records, not new verification of those releases.

Current source review does not establish new runtime proof for every host, API fixture, provider, or financial workflow. Package-specific compatibility and testing requirements remain in the integration guides.

SoundSync

Verified platform releases

Earlier releases are retained here as historical records. Consult the current feature and compatibility guides before integrating.

2026-07-25

Plugin credential contract documentation, JUCE licensing examples, API final release audit, OpenAPI expansion, and release gates verified.

2026-07-25

Team Accounts production release, product-scoped RBAC, and session revocation verified.

2026-07-25

Subscription Bundle checkout, upgrades and downgrades, proration, scheduled subscription changes, and customer library bundle states verified.

2026-07-24

Commerce, marketplace, operations, marketing, storefront/embed, webhooks, billing, and API documentation coverage backfilled from verified Phase 4 reports.