Guide
Account Security
Password changes, two-factor authentication, recovery codes, and workspace access.
SoundSync
Set up an authenticator
-
Open account security
Sign in to your own account and open the security controls in Settings. Keep account credentials separate from product keys and reseller tokens.
-
Confirm your password
Enter your current account password to begin two-factor setup. The setup secret is private; do not send it to support or include it in a screenshot.
-
Add the account to your authenticator
Use the displayed setup information in your authenticator application. Generating a secret does not enable protection yet.
-
Confirm enrollment
Enter the current six-digit authenticator code and finish the enable action. Wait for confirmation before leaving Settings.
-
Save the recovery codes
Copy the returned recovery codes to a private password manager or secure offline location. Each code is a single-use fallback; SoundSync stores hashes rather than recoverable copies.
-
Check the next sign-in
Use your email and password, then complete the two-factor challenge with a current authenticator code. Do not close your existing signed-in session until you have confirmed the new method works.
SoundSync
Find the account security controls
Account settings brings two-factor status, recovery-code counts, sessions and password changes together. The example shows empty password fields and no setup keys or recovery codes.
SoundSync
Customer serial redemption
Use a recovery code when the authenticator is unavailable
At the two-factor sign-in challenge, use an unused recovery code instead of an authenticator code. A successfully used recovery code cannot be used again. Keep track of which codes remain and do not share them with a teammate.
If a time-based code is rejected, check the authenticator account and automatic device time, then use a newly generated code. Repeatedly requesting setup or changing unrelated product credentials does not repair an account sign-in challenge.
SoundSync
Replace a lost or compromised authenticator
-
Recover access
Complete sign-in with an unused recovery code if your authenticator is unavailable.
-
Remove the old factor
In account security, disabling two-factor authentication requires your current password and a valid authenticator or recovery code.
-
Enroll the replacement
Start setup again, confirm a code from the replacement authenticator, and store the newly returned recovery codes. Do not rely on the old recovery set.
-
Review access
Change a compromised account password and review team roles and product access. Removing a person from a workspace is separate from changing your own factor.
If no authenticator or recovery code remains
Contact support@soundsyncsolutions.biz from your account email and explain that you cannot complete two-factor sign-in. Do not include a password, setup secret, recovery code, serial, or payment-card details. Account recovery requires review; this guide does not promise an automatic bypass or a completion deadline.
A password-reset email is not a promise that two-factor protection will be removed. Protect access to the email account as well as the SoundSync account.
Personal account protection and team access are separate
Two-factor authentication protects the account that enabled it. This is not an organization-wide enforced-MFA policy. Team members use individual accounts with scoped roles and product assignments; do not distribute the owner password or recovery codes.
Account closure and personal-data deletion are support-reviewed procedures, not a self-service delete or session-management API advertised by this guide.
SoundSync
Account sign-in and security calls
These are the current first-party account calls used by account settings and sign-in. They are not an OAuth provider, an organization-wide MFA API, or a replacement for plugin product credentials. Self-service session revocation and account deletion are not advertised here.
/api/auth/login
Sign in or complete a two-factor challenge
- Auth
- Public request; operation-specific verification still applies
- Scope
- Only the matching verified account.
- Request fields
- email: string (required)
- password: string
- twoFactorToken: string
- twoFactorCode: string
- role: string
- storefrontSlug: string
- marketingOptIn: boolean
- marketingOptOut: boolean
- accountType: customer | developer | reseller | owner | admin | support | platform. Login-record selection hint only, not an asserted role or permission. platform selects a non-customer account when a separate customer account shares the email.
- Returns
- 200: account result and token, or twoFactorRequired and twoFactorToken. A challenge token is not an account session.
- Notes
- A wrong or expired challenge returns 401. Never store or log the password, authenticator setup secret, recovery code, or tokens in public examples. Send storefrontSlug for a saved store-local credential and keep it through any two-factor continuation. The returned store-only token cannot authorize another store or global security settings. Product-scoped customer-token activation checks that the developer matches and still requires ownership/device proof. Generated native packages retain their documented shared-customer login flow. Omit storefront context and use the original shared credentials for shared SoundSync login. Existing two-factor and inbox verification requirements remain. Marketing choice compatibility fields do not require a new opt-in checkbox. For team invitation sign-in, use the developer/platform login context. accountType and its account_type alias select the login-record family, not the role granted after authentication. Separate customer and developer records may share an email. Complete existing password/2FA checks and invitation acceptance; a matching email alone grants no workspace membership.
Request, response and error reference
Request (application/json)
{
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email"
},
"password": {
"type": "string"
},
"twoFactorToken": {
"type": "string"
},
"twoFactorCode": {
"type": "string"
},
"role": {
"type": "string"
},
"storefrontSlug": {
"type": "string"
},
"marketingOptIn": {
"type": "boolean"
},
"marketingOptOut": {
"type": "boolean"
},
"accountType": {
"type": "string",
"enum": [
"customer",
"developer",
"reseller",
"owner",
"admin",
"support",
"platform"
],
"description": "Login-record selection hint only, not an asserted role or permission. platform selects a non-customer account when a separate customer account shares the email."
}
},
"required": [
"email"
],
"additionalProperties": true,
"anyOf": [
{
"required": [
"password"
]
},
{
"required": [
"twoFactorToken",
"twoFactorCode"
]
}
]
}
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"token": {
"type": "string"
},
"session": {
"type": "object",
"properties": {
"expiresAt": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"expiresInSeconds": {
"type": "integer",
"minimum": 0
},
"refreshSupported": {
"const": false
}
},
"additionalProperties": true
},
"user": {
"type": "object",
"properties": {
"storefrontSession": {
"type": "boolean"
},
"storefrontDeveloperId": {
"type": "integer",
"minimum": 1
}
},
"additionalProperties": true
},
"twoFactorRequired": {
"type": "boolean"
},
"twoFactorToken": {
"type": "string"
},
"code": {
"type": "string"
},
"message": {
"type": "string"
}
},
"additionalProperties": true
}
Documented failures: 400, 401, 403, 500, 503.
/api/account/security
Read your account security status
- Auth
- Account Bearer session token
- Scope
- The signed-in personal account only; not an effective developer workspace or product assignment.
- Returns
- 200: current account security status.
- Notes
- Shared-account responses retain the saved customer, developer, owner, admin, support or reseller role; legacy rows without a role use the existing admin/reseller fallback. This identity label does not grant workspace permissions. A store-only session returns user.storefrontSession:true, its store identifiers, security.storefrontOnly:true and sharedAccountSettingsAvailable:false instead of shared two-factor or session counts. Use shared sign-in for global security settings. A failed session-count query returns 500 Failed to load security settings instead of presenting a fabricated zero. Treat the count as unavailable on failure; a successful response reports the saved-session count, not proof that every session is currently online.
Request, response and error reference
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"user": {
"type": "object",
"properties": {
"id": {
"type": "integer",
"minimum": 1
},
"email": {
"type": "string",
"format": "email"
},
"firstName": {
"type": [
"string",
"null"
]
},
"lastName": {
"type": [
"string",
"null"
]
},
"role": {
"type": "string",
"description": "The saved personal account role, not a workspace membership role or authorization grant."
},
"storefrontSession": {
"type": "boolean"
},
"storefrontDeveloperId": {
"type": "integer",
"minimum": 1
},
"storefrontCustomerId": {
"type": "integer",
"minimum": 1
}
},
"additionalProperties": true
},
"security": {
"type": "object",
"properties": {
"twoFactorEnabled": {
"type": "boolean"
},
"twoFactorSetupPending": {
"type": "boolean"
},
"recoveryCodesRemaining": {
"type": "integer",
"minimum": 0
},
"activeSessionCount": {
"type": "integer",
"minimum": 0
},
"twoFactorEnabledAt": {
"type": [
"string",
"null"
]
},
"storefrontOnly": {
"type": "boolean"
},
"sharedAccountSettingsAvailable": {
"type": "boolean"
}
},
"additionalProperties": true
}
},
"additionalProperties": true
}
Documented failures: 401, 404, 500, 503.
/api/account/2fa/setup
Begin authenticator enrollment
- Auth
- Account Bearer session token
- Scope
- The signed-in personal account only; not an effective developer workspace or product assignment.
- Request fields
- currentPassword: string (required)
- Returns
- 200: secret, otpauthUrl, issuer. Treat the entire response as private.
Request, response and error reference
Request (application/json)
{
"type": "object",
"properties": {
"currentPassword": {
"type": "string"
}
},
"required": [
"currentPassword"
],
"additionalProperties": true
}
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"secret": {
"type": "string"
},
"otpauthUrl": {
"type": "string"
},
"issuer": {
"const": "SoundSync"
}
},
"additionalProperties": true
}
Documented failures: 401, 404, 500, 400, 409, 503.
/api/account/2fa/enable
Confirm a code from the pending authenticator
- Auth
- Account Bearer session token
- Scope
- The signed-in personal account only; not an effective developer workspace or product assignment.
- Request fields
- code: string (required)
- Returns
- 200: message and single-use recoveryCodes. Save them privately.
- Notes
- Personal account enrollment, not a workspace operation. The pending secret is checked under a row lock and consumed in the same transaction that saves the verified authenticator and recovery hashes. Concurrent or repeated enable requests return 409 after one succeeds; they do not rotate a live factor or return another recovery set. An invalid code or failed save leaves enrollment uncommitted.
Request, response and error reference
Request (application/json)
{
"type": "object",
"properties": {
"code": {
"type": "string"
}
},
"required": [
"code"
],
"additionalProperties": true
}
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"message": {
"type": "string"
},
"recoveryCodes": {
"type": "array",
"items": {
"type": "string"
}
}
},
"additionalProperties": true
}
Documented failures: 400, 401, 404, 409, 500, 503.
/api/account/2fa/disable
Disable your enrolled authenticator
- Auth
- Account Bearer session token
- Scope
- The signed-in personal account only; not an effective developer workspace or product assignment.
- Request fields
- currentPassword: string (required)
- code: string (required)
- Returns
- 200: confirmation message.
Request, response and error reference
Request (application/json)
{
"type": "object",
"properties": {
"currentPassword": {
"type": "string"
},
"code": {
"type": "string"
}
},
"required": [
"currentPassword",
"code"
],
"additionalProperties": true
}
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"message": {
"type": "string"
}
},
"additionalProperties": true
}
Documented failures: 401, 404, 500, 400, 503.
SoundSync
Recover a customer sign-in
| What you see | What to do |
|---|---|
| Purchased before, but never created a password | Choose Reset password on the same storefront and use your purchase email to set up access. Do not create another purchase to recover an existing product. |
| The browser could not save your sign-in session | Allow required site data/storage for this website, check browser privacy or storage restrictions, and retry. The page verifies that the session was saved before opening the account. |
| Email or password rejected | Check the purchase email and the intended customer/developer sign-in. Use Reset password if needed. The form keeps entered values and supports retry. |
| Email verification or authenticator requested | Complete that specific challenge. A verification notice or two-factor challenge is not a completed session, and a password reset does not bypass two-factor authentication. |
| Connection, service, or rate-limit error | Follow the visible recovery message and wait where required. Repeated submissions do not repair a network problem; avoid creating duplicate accounts or purchases. |
Return to the intended store
Use the recovery link on the storefront where you are trying to sign in. Its supported store and return path are retained so recovery can lead back to the intended product or account. Keep reset links private. Browser storage is required for the saved sign-in session. Developer-configured GA4 on eligible custom-domain public pages runs automatically; it is separate from sign-in storage and does not honor a saved analytics decline.
Customer details belong to the relevant store
Authorized developers can correct customer names, email and phone and, for a linked customer account, set a password for their own storefront relationship. These edits do not change the shared SoundSync login, another developer storefront, shared verification, or shared account recovery.
A changed store email or password invalidates earlier sessions and reset links issued for that store credential. The customer signs in using the corrected email in that storefront. Store-only sessions cannot manage global account security or use another store; the shared SoundSync account remains the route for platform-wide settings and integrations.
Email corrections update the store marketing contact, supported pending email work and current store contact references, including support, serial and order contact fields. Later marketing activity and imports retain the corrected store details. Customer edits to the shared SoundSync profile update shared contact records without replacing separate store details. Sent email, issued invoices and payment-provider history remain historical records.
First and last names can be cleared independently. Workspace-wide contact editing requires the existing customers.manage permission and all-products scope. Contact corrections do not transfer purchases, rewrite issued invoices, change refund eligibility or clear marketing restrictions. Last Login records sign-in activity, not a support edit.
When a session cannot be checked
A signed account token must still match an active stored session. Revoked sessions return 401 SESSION_REVOKED. If the session store cannot be checked, protected account requests stop with 503 SESSION_VERIFICATION_UNAVAILABLE rather than continuing with unverified access.
Retry after a temporary availability problem. Do not treat 503 as permission to bypass authentication or automatically create a second payment, refund or other financial action. Reconcile the specific operation before repeating a write. Product credentials and customer library tokens have separate authentication contracts.
SoundSync
Account API reference
Accounts and recovery
Registration, reset, sign-out and verified profile changes.
Password changes, recovery codes and sign-out
A successful password change saves the new password and revokes the other stored account sessions together. If revocation fails, the password change is rolled back and the request fails. With a recognized current token, that session is retained; without one, all stored sessions for the account are revoked.
Recovery codes are single-use, including concurrent attempts: only the request that consumes the code can complete that recovery-code sign-in. Disabling two-factor authentication checks the current password and factor against locked current account state. A failed logout returns 503 SESSION_REVOCATION_UNAVAILABLE, not a completed sign-out. Retry and do not treat client-side token removal as confirmation that the server session was revoked.
Confirm enrollment once
Setup and enable actions are serialized against the current account state. Confirm a code from the latest setup. Only one concurrent enable can succeed; a repeated enable returns 409 and does not replace the active authenticator or return a second recovery set. Starting setup on an already enabled account also returns 409. Recover or disable the existing factor before enrolling a replacement.
Native account login with two-factor authentication
The updated JUCE 0.9.3 and HISE Native C++ 0.5.2 sources support the customer account two-factor challenge. Regenerate the complete package, replace the matching sources and rebuild the plugin; an older installed binary does not acquire this behavior from a documentation or server update.
Sign in with the customer email and password. If two-factor authentication is enabled, the account form changes to Authenticator or recovery code. Enter a current authenticator code or an unused recovery code and choose Verify code. A challenge is not a customer session, entitlement or device activation; the plugin remains locked until verified account login and product/device activation succeed.
An invalid code can be retried. An expired challenge requires signing in again. The challenge lasts up to ten minutes and is kept only in the running native client, not the activation cache, logs or public state. Account passwords, two-factor codes and account session tokens are not saved in the license cache. Do not disable two-factor protection to integrate a plugin.
Account sessions must be verifiable
A signed account token is not enough on its own: customer account requests also check that the session is still allowed. If that check is unavailable, protected library, invoice, review, device-reset, download and customer-token activation requests stop before returning private data or performing the protected action.
503 SESSION_VERIFICATION_UNAVAILABLE means verification could not finish. Retry after service recovery; it does not mean that the purchase disappeared or the session was confirmed revoked. A confirmed revoked session returns 401 LIBRARY_SESSION_REVOKED and requires sign-in again. Do not grant access on either response.
Shared library/download tokens retain their separate token and ownership checks. Optional storefront personalization can fall back to anonymous browsing when customer identity cannot be established; that does not authorize a private download. This account-session check does not replace the signed JUCE offline-grant policy.
Choose store or shared-account recovery
A storefront email/password override is valid only with that storefront context. Send storefrontSlug when requesting its password reset. Store resets are one-use, expire after 60 minutes and leave shared-account credentials unchanged. Email or password changes supersede earlier store reset links.
Shared-account customer profile email edits take effect immediately; they do not prove inbox ownership. Platform/developer email changes use the separate verified pending-change procedure. A store profile edit remains local, and a store password change requires signing in again. Store credentials retain the linked account two-factor challenge; they do not disable or replace global two-factor settings.
SoundSync suspension and store restrictions
A SoundSync-wide customer-account suspension blocks customer library and download authorization, including requests made with an existing signed-in session. A restriction imposed by one store remains scoped to that store; unrelated stores remain available unless the SoundSync account is also suspended.
Suspension does not delete purchase history or create a refund. Contact SoundSync support about a platform restriction and the developer about a store restriction. A previously issued storage link can remain usable until it expires; already downloaded files cannot be recalled by an account restriction.
