Identity verification, the changelog default, usage and warnings
GET /v1/notifications/settings
GET
/v1/notifications/settings
Whether browser calls must prove their user (require_user_hash), whether new changelog entries post to the bell by default, whether a signing secret exists (never the secret), this month’s usage, and warnings such as identity verification being off.
Auth: Secret key only. The dashboard has the same operation under /v1/dashboard/notifications.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”Settings
object
data
object
require_user_hash
boolean
changelog_to_bell_default
boolean
legacy_unverified
True while require_user_hash is off.
boolean
signing_secret
Never the secret itself.
object
configured
boolean
created_at
string | null
previous_valid_until
Set for 24 hours after a rotation, while the old secret still verifies.
string | null
usage
object
month
string
Example
2026-09 sent
integer
limit
integer
remaining
integer
poll_interval_seconds
integer
warnings
Array<string>
error
null
meta
object
Error envelope. See error.code for the discriminator.
object
data
required
null
error
required
object
code
required
string
message
required
string
remediation
required
string
doc_url
string format: uri
param
string
request_id
string
meta
object
key
additional properties
Error envelope. See error.code for the discriminator.
object
data
required
null
error
required
object
code
required
string
message
required
string
remediation
required
string
doc_url
string format: uri
param
string
request_id
string
meta
object
key
additional properties
Error envelope. See error.code for the discriminator.
object
data
required
null
error
required
object
code
required
string
message
required
string
remediation
required
string
doc_url
string format: uri
param
string
request_id
string
meta
object
key
additional properties