Walletguide
DevelopersAPIReferencenotifications

Read

Read (notifications endpoint) in the Walletguide REST API. Parameters, response fields, and a playground you can run.

POST
/wallets/{walletId}/notifications/{id}/read

Authorization

bearerAuth
Authorization<token>

A Walletguide API key (wg_…) or an OAuth bearer token. Paste the value only. Create a key under Wallet settings → API keys.

In: header

Path Parameters

walletId*string

Row uuid

Formatuuid
id*string

Row uuid

Formatuuid

Response Body

application/json

application/json

curl -X POST "https://example.com/wallets/497f6eca-6276-4993-bfeb-53cbbbba6f08/notifications/497f6eca-6276-4993-bfeb-53cbbbba6f08/read"
{  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "walletId": "0ecad4a2-3549-43fb-807e-9ff033247480",  "firestoreId": "string",  "type": "string",  "recipientUserId": "string",  "readTime": "2019-08-24T14:15:22Z",  "payload": {    "property1": null,    "property2": null  },  "createdTime": "2019-08-24T14:15:22Z",  "createdUserId": "string",  "lastUpdatedTime": "2019-08-24T14:15:22Z",  "lastUpdatedUserId": "string"}

Create notification

Only the client-produced social types (assigned user, comments). The payload is a display snapshot stored verbatim; the recipient must be a wallet member.

MarkRead

Bulk read-state toggle (legacy markNotificationsAsRead / markNotificationsAsUnread). User sessions can only touch their own notifications.