Guide
Developer Notice Inbox
Read billing, email and product notices; understand unread state, workspace access and unavailable checks.
One inbox for issues you can act on
The bell in the developer header gathers current billing, email-sending and published-product issues, with links to the relevant workspace. It is separate from Plugin Notices, which deliver product messages inside supported plugins.
Open the inbox to review an item, follow its action link, or use Mark all as read. Read items remain visible while their issue is active. A changed issue can become unread again; resolved issues disappear after a successful refresh.
SoundSync
What each source checks
| Source | Relevant issue | Access boundary |
|---|---|---|
| Billing | An unpaid bill or missing billing payment method | billing.view and all-products scope; changing billing still requires its existing management permission |
| Email sending | Held Growth Flow recipients or a paused campaign with queued recipients | marketing.view and all-products scope; only available billing details are linked |
| Products | Incomplete published-product setup or a rejected/suspended product or listing | products.view and the teammate's assigned products |
SoundSync
Developer dashboard
Read a warning without turning it into a failure
A notice explains a recorded issue, not continuous monitoring or proof that every customer license is healthy. Missing historical plugin-test evidence alone does not become a live connection failure, and a JUCE product does not need a HISE package.
Some checks are unavailable means a source could not be checked. An empty inbox with an unavailable source is not a verified all-clear. If a refresh fails, the interface can retain the last checked notices and identify the failure. Refresh again after recovery; do not treat old notices as current provider confirmation.
Unread is local; resolved is an account condition
The maintained interface saves notice ID/revision/severity read markers in this browser, separately for the signed-in account and workspace. Another browser can have a different unread badge. Clearing browser storage can clear those markers; marking read does not fix billing, send an email or dismiss an active server issue.
Changing accounts, workspace access or leaving the developer area clears the active private notice display. The developer interface refreshes periodically while active and offers Refresh. Server results can be cached for up to 60 seconds within their permission/product context; this is not a real-time uptime or delivery guarantee.
Choose the account with workspace access
Choose a developer account means the current signed-in account has no developer workspace. Use the store owner's developer login or the account invited to its team. Platform-owner access alone is not a developer workspace.
Workspace access needs attention can mean inactive membership or an inactive selected workspace. Contact its owner or use another account with active access. This account notice is generated locally from session discovery, without repeatedly requesting private workspace notices or provisioning a workspace.
SoundSync
Read the current workspace notices
/api/developer/notifications
Read actionable billing, email and product notices for the permitted workspace
- Auth
- Account Bearer session token
- Scope
- workspace.view and active selected-workspace access. Billing and email sources require all-products scope and billing.view/marketing.view respectively. Product notices require products.view and stay assigned-product scoped. Additional sources use existing orders, refunds, customers, serials, domains, payouts, team, API/webhook and partner permissions; private details remain permission-filtered.
- Returns
- HTTP 200: workspaceId, developerId, checkedAt, unavailable, notices, activity, activityWindowDays, activityLimit.
- Notes
- Read-only: does not create a billing customer, change cards, reserve spend, dispatch email or send money. notices contains current actionable checks; unavailable names sources that could not be checked. An empty list is not proof of healthy sources when unavailable is nonempty. Source results can be cached for 60 seconds per effective developer, workspace, permission set and product scope; checkedAt is the collection time, not a telemetry guarantee. Successful responses are private,no-store. Read state is kept by the maintained browser client, not written through this endpoint; marking read does not resolve the issue. A workspace-required account notice is generated locally after session discovery and is not a successful response from this endpoint. Historical missing plugin-test evidence alone does not produce a live connection-failure notice. Notices and Activity are separate. Activity contains at most 50 grouped updates from the last 14 days and does not increase the warning count. Durable incident and milestone state is separate from browser-local unread markers. Resolution/retry/deadline fields are informational; reading or marking read never retries work, dismisses an active issue or changes account permissions.
Request, response and error reference
No request body fields are read by this operation.
HTTP 200 response (application/json)
{
"type": "object",
"properties": {
"workspaceId": {
"type": "integer",
"minimum": 1
},
"developerId": {
"type": "integer",
"minimum": 1
},
"checkedAt": {
"type": "string",
"format": "date-time"
},
"unavailable": {
"type": "array",
"items": {
"type": "string"
}
},
"notices": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"severity": {
"type": "string",
"enum": [
"warning",
"error"
]
},
"title": {
"type": "string"
},
"message": {
"type": "string"
},
"href": {
"type": "string"
},
"actionLabel": {
"type": "string"
},
"revision": {
"type": "string"
},
"retryText": {
"type": "string"
},
"resolution": {
"type": "string"
},
"incidentId": {
"type": [
"string",
"null"
]
},
"urgency": {
"type": [
"string",
"null"
]
},
"affected": {
"type": "array",
"items": {
"type": "object",
"properties": {
"label": {
"type": "string"
},
"href": {
"type": "string"
},
"reason": {
"type": "string"
},
"retryText": {
"type": "string"
},
"resolution": {
"type": "string"
},
"nextRetryAt": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"deadlineAt": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"count": {
"type": "number"
},
"unit": {
"type": "string"
}
},
"additionalProperties": true
}
}
},
"additionalProperties": true,
"required": [
"id",
"severity",
"title",
"message",
"href",
"actionLabel",
"revision"
]
}
},
"activity": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"severity": {
"const": "info"
},
"tone": {
"type": "string",
"enum": [
"info",
"success"
]
},
"category": {
"type": "string"
},
"title": {
"type": "string"
},
"message": {
"type": "string"
},
"href": {
"type": "string"
},
"actionLabel": {
"type": "string"
},
"occurredAt": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"count": {
"type": "number"
},
"revision": {
"type": "string"
},
"retryText": {
"type": "string"
},
"resolution": {
"type": "string"
}
},
"additionalProperties": true
}
},
"activityWindowDays": {
"const": 14
},
"activityLimit": {
"const": 50
}
},
"additionalProperties": true,
"required": [
"workspaceId",
"developerId",
"checkedAt",
"unavailable",
"notices"
]
}
Documented failures: 400, 401, 403, 500, 503.
Interpret the response before showing an all-clear
workspaceId and developerId identify the checked workspace; checkedAt is its collection time. notices contains id, severity, title, message, href, actionLabel and revision. unavailable lists sources that failed to load. Do not merge notices from different accounts or product scopes.
The read does not create billing customers, update cards, reserve email spend, send mail or execute payments. A successful response is private,no-store. Missing authentication returns 401; denied workspace access returns 403; a failed overall collection can return 503. The API does not save read markers: those belong to the browser interface.
SoundSync
Resolve the underlying issue
Separate active issues from recent progress
The header now has Notices and Activity. Notices group actionable issues with affected items, the recorded cause, next retry and resolution guidance when available. Activity shows up to 50 grouped updates from the last 14 days, including permitted team/partner changes, successful work and milestones. Activity does not increase the warning count.
The unread warning count and activity indicator are different. Read markers stay local to this browser/account/workspace. Durable incident and milestone state is separate: marking read does not dismiss an active issue, retry a job or resolve a failed operation. A source marked unavailable is not an all-clear. Private details still depend on the teammate's existing permissions and product assignment.
