Set Notification Preference - Pacifica

POST /api/v1/account/notifications/preferences

This endpoint turns one channel on or off for the notification types that you send. Pacifica changes all the types together or none of them. Other channels keep their current value. A channel also needs to be on in the master preference. See Set notification master preference.

Operation Type (for Signing)

Header Field	Type	Content
`"type"`	string	`"set_notification_preference"`

Request Body

Field	Type	Need	Description	Example
`”account”`	string	required	User’s wallet address	`42trU9A5…`
`“signature”`	string	required	Cryptographic signature	`5j1Vy9Uq…`
`“timestamp”`	integer	required	Current timestamp in milliseconds	`1716200000000`
`”notification_types”`	array	required	One or more notification types: `“deposit_success"` `"withdraw_success"` `"order_filled"` `"order_partially_filled"` `"order_canceled"` `"tp_sl_triggered"` `"liquidation"` `"strategy_update”`	`[“order_filled”]`
`“channel”`	string	required	Channel to change: `“in_app"` `"mobile_push"` `"web_push”`	`mobile_push`
`”enabled”`	boolean	required	`true` turns the channel on. `false` turns it off	`true`
`”expiry_window”`	integer	optional	Signature expiry in milliseconds	`30000`
`”agent_wallet”`	string	optional	Agent wallet address	`69trU9A5…`

{
  "account": "42trU9A5...",
  "signature": "5j1Vy9Uq...",
  "timestamp": 1716200000000,
  "notification_types": ["order_filled", "tp_sl_triggered", "liquidation"],
  "channel": "mobile_push",
  "enabled": true,
  "expiry_window": 30000
}

You can’t set a preference for test or for types that Pacifica doesn’t send. See Notification types. You can sign this request with the account key or with an agent wallet.

Response

Status 200: Preference updated. The response has all your preferences after the change, in the same format as List notification preferences

{
  "success": true,
  "data": {
    "master_enabled_channels": ["in_app", "mobile_push"],
    "preferences": [
      { "notification_type": "deposit_success", "enabled_channels": [] },
      { "notification_type": "withdraw_success", "enabled_channels": [] },
      { "notification_type": "order_filled", "enabled_channels": ["mobile_push"] },
      { "notification_type": "order_partially_filled", "enabled_channels": [] },
      { "notification_type": "order_canceled", "enabled_channels": [] },
      { "notification_type": "tp_sl_triggered", "enabled_channels": ["mobile_push"] },
      { "notification_type": "liquidation", "enabled_channels": ["mobile_push"] },
      { "notification_type": "strategy_update", "enabled_channels": [] }
    ]
  },
  "error": null,
  "code": null
}

Status 400: Invalid request parameters or signature. An empty notification_types list, or a type that you can’t configure, returns this error:

{
  "success": false,
  "data": null,
  "error": "notification_types must not be empty",
  "code": 400,
  "error_id": "invalid_notification_types"
}

Status 403: The account doesn’t exist. An account exists after its first deposit
Status 429: Rate limit exceeded
Status 500: Internal server error

Code Example (Python)

import requests

payload = {
    "account": "42trU9A5...",
    "signature": "5j1Vy9Uq...",
    "timestamp": 1716200000000,
    "notification_types": ["order_filled", "tp_sl_triggered", "liquidation"],
    "channel": "mobile_push",
    "enabled": True
}

response = requests.post(
    "/api/v1/account/notifications/preferences",
    json=payload,
    headers={"Content-Type": "application/json"}
)

data = response.json()