Skip to main content
POST
Configure Web Push contact settings and optionally rotate server-generated VAPID keys.
Configure Web Push contact settings and optionally rotate server-generated VAPID keys. Credentials are write-only: submitted directly without preparation, queued payloads or credential echoes. This changes provider configuration immediately; inspect push_providers_list before retrying an uncertain result. Requires a scoped personal key, an explicit granted project_id, and push_providers.write. Current role and credential grants remain enforced. See Agent messaging and project operations for authorization and recovery.

Authorizations

Authorization
string
header
required

Integration key for backend workloads, or a scoped personal key (sr_user_) for account discovery and supported project operations. MCP accepts only personal keys.

Headers

X-Sendrealm-Project-Id
string<uuid>
required

Body

application/json
app_id
string<uuid>
required

Push app UUID from push_apps_create or push_apps_list in this project.

Required string length: 1 - 36
web_vapid_subject
string

VAPID contact URI, such as mailto:push@example.com.

Required string length: 1 - 2048
regenerate_web_vapid_keys
boolean

Generate replacement VAPID keys. Existing browser subscriptions can stop working; omitted preserves existing keys.

Response

Authorized result, preparation, or durable execution receipt.

status
integer
required
data
object
required