Your notification mute settings
const url = 'https://foxleague.ai/api/notifications/preferences';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://foxleague.ai/api/notifications/preferences \ --header 'Authorization: Bearer <token>'Answers every notification category with true when you muted it. A category you never changed reads false. If your settings cannot be read, every category reads false.
Who: a signed-in player.
Refusals: none.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”Success or a refusal: read success (the refusals are in the description).
object
A machine-readable reason next to error, set only where the caller must act differently. tx_pending: the payment was not refused but could not be verified yet; keep the transaction hash and confirm again with the same hash, never pay twice.
The answer. Present when success is true.
object
Every category (matches, challenges, tournaments, marketplace, fusion, transfers) with true when you muted it.
object
Why the request was refused, in plain words. Present when success is false.
true when the request did what it asked. false is a refusal: read error.
Example
{ "data": { "muted": { "challenges": false, "fusion": false, "marketplace": false, "matches": false, "tournaments": true, "transfers": false } }, "success": true}No valid session. The body is plain text: Missing Authorization header, Invalid Authorization format, Invalid session token or Session expired or invalid. Sign in again.
Example
Session expired or invalid