Guide
Test Connection Troubleshooting
Diagnose product connectivity rather than customer entitlement.
Test product connectivity, not ownership
POST /api/plugin-connections/verify with productId and appId from the same saved product. Standard clients send pluginKey/pluginSecret in JSON; generated native clients send their matching publicClient identity. Licensing headers are not substituted into this endpoint.
Test Connection does not activate a customer, validate a purchase, reserve a device or create an offline grant. Missing manual-test history alone is not proof that a working JUCE plugin is disconnected.
SoundSync
Connection failure checklist
| Result | Action |
|---|---|
| Wrong product or credentials | Compare the generated product/app/environment tuple and current package. Do not rotate credentials just to clear historical warnings. |
| Timeout / unavailable service | Check the HTTPS base URL and retry after recovery. A diagnostic failure is not a licensing decision. |
| Connection works but access fails | Test activation/validation with customer entitlement and machine proof. |
| Old last-seen time | Distinguish recorded history from current health; stale success is not a live health check. |
SoundSync
Connection contract
Plugin Connection Verification
Body fields, identities and response meaning.