DELETE/notifications

Mark notifications as read

Marks the specified notifications as read/seen for the authenticated user. Once marked as read, notifications will no longer appear in GET /notifications.

Base URL: https://clob.polymarket.com
Auth: L2 API credentials (key, secret, passphrase)POLY_API_KEY, POLY_ADDRESS, POLY_SIGNATURE, POLY_PASSPHRASE, POLY_TIMESTAMP
Rate limit: 125 req / 10s (12.5 per second)
Limit applies to: /notifications

Parameters

Name	In	Type	Required	Description
ids	query	string	yes	Comma-separated list of notification IDs to mark as read

Example

curl -X DELETE "https://clob.polymarket.com/notifications?ids=<ids>" \
  -H "POLY_API_KEY: $POLY_API_KEY" \
  -H "POLY_ADDRESS: $POLY_ADDRESS" \
  -H "POLY_SIGNATURE: $POLY_SIGNATURE" \
  -H "POLY_PASSPHRASE: $POLY_PASSPHRASE" \
  -H "POLY_TIMESTAMP: $POLY_TIMESTAMP"

L2 requests are signed with HMAC-SHA256 using your API secret, and the timestamp is part of the signature, so keep the machine's clock accurate. A missing credential or a stale signature both come back as Unauthorized/Invalid api key. The Python SDK signs for you.

Responses

Status	Meaning
200	Notifications successfully marked as read
400	Bad request - Invalid ids
401	Unauthorized - Invalid API key or authentication failed
500	Internal server error

Related endpoints

GET /notifications CLOB API

Polymarket's API serves current state only, so it cannot show what a market's book looked like after it resolved. PolyTest records Up/Down markets while they run and keeps the snapshots. Try it free, or read the full rate limit reference.

From Polymarket's published OpenAPI spec and rate-limit tables, synced 2026-10-04.