Guide
Plugin Connection Verification
POST /api/plugin-connections/verify checks the saved product/app integration, not customer access.
Generated native clients use public identity
HISEScript/custom HTTP use the standard product key/secret path. Current native HISE and JUCE packages identify the generated app/product through the supported hise-native or juce-native public-client contract and keep pluginSecret out of public configuration. Product identification is not customer ownership proof; do not substitute a developer token.
SoundSync
Request body
| Field | Use |
|---|---|
| productId | Saved product identity; product_id is accepted as an alias |
| appId | Generated app identity; app_id is accepted as an alias |
| pluginKey / pluginSecret | Standard credential path for HISEScript/custom HTTP |
| publicClient | Supported hise-native or juce-native contract for generated native clients |
| pluginVersion | Optional package/version diagnostic context |
| environment | Optional environment diagnostic context |
Standard versus native identity
Use the standard credential fields for the standard path. Current native packages identify their matching public app/product without distributing pluginSecret in public configuration. The public identity must still match the saved product; it is not customer proof.
The endpoint records integration connection status and returns the verification result. It does not grant ownership, activate a customer device, or prove exported audio enforcement.
SoundSync
Illustrative native connection body
{
"productId": 123,
"appId": "DEMO_APP",
"publicClient": "juce-native",
"pluginVersion": "0.7.0"
}Example evidence
The values above are placeholders describing the source contract, not a seeded production response. Use the matching generated package and test privately.