Skip to content
SoundSyncAudio software platform

Documentation

SvelteKit Website Integration

Connect SvelteKit to SoundSync customer access without replacing your existing website.

Use adapter-node and the correct asset directory

Merge src/routes/api/soundsync/[action]/+server.js, lib/ and the portal component. Use adapter-node and set ORIGIN to the exact HTTPS website. Copy public/soundsync into static/ if that is your configured asset directory. ADDRESS_HEADER or the explicit trusted-client-IP header must come only from your trusted overwritten proxy header.

Save callbacks that your application actually serves

The verification, reset, login, success and cancel callbacks are /api/soundsync/verify, /reset-password, /account, /checkout/complete and /checkout/cancel. Serve the actual routes and keep private account/API responses out of caches.

Choose the payment model before installing

The general framework download is configured for Full Store with SoundSync payments and tax. To keep an external provider, choose its separate Keep external checkout download and guide, or deliberately implement external mode with a matching connection. A framework choice never authorizes a different payment flow.

SoundSync

Complete the setup

Website setup checklist

TXT verification, key rotation, private sessions, hosted testing and migration boundaries.

HTTP contract

Accounts, tax evidence, checkout confirmation and downloads.

External licensing

Provider-specific one-time perpetual purchase handling.