APIEndpoint referenceValue bet reports
/value-bet-reports
What the community has flagged about a set of bets, and what the caller flagged themselves.
What the community has flagged about a set of bets, and what the caller flagged themselves.
The result is keyed "playerId_matchId" so a client can look up a bet it is already rendering without scanning a list.
AuthorizationBearer <token>
Supabase access token.
In: header
Query Parameters
matchIds?string
playerIds?string
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/value-bet-reports"{ "bets": null}/value-bet-lineup-alerts DELETE
The identifiers come from the request body, not the query string, which is unusual for a DELETE but is what the client sends.
/value-bet-reports POST
One report per user per bet: filing again replaces the previous one rather than stacking, so one user cannot inflate a community count.