WagerStreet · GSWallet API v1.0 · what to change on the key
The 22 operations we are asking to have changed on our partner key: 15 reads that answer 403 today, 5 write operations our operator desks call, and 2 we could not verify. The 50 operations that already work are listed, with everything else, on the full access request; this page is that request’s sections B, C and D on their own.
What we are asking. Please grant read access to the operations marked 403 blocked, grant write scope for the write operations, and confirm the unverified ones are in scope for this partner. Nothing that already works needs to change — the 50 working operations are on the full page for reference, and the other 334 operations in the catalog are not requested at all.
Auth as it stands. The key needs both headers together — x-api-key and x-partner-id — and either one alone answers 403. Partner id and key are deliberately not printed here.
Priority. critical operations are called unattended, on a schedule, by services with nobody at a keyboard — losing one breaks a data pipeline or an alert feed. high ones are called when a member of staff uses a console (every write is in this class — nothing writes unattended). standard ones are exposed in an endpoint explorer and called only by hand.
Operations that do not exist in the catalog at all are not on this page — they are specified separately as The Dream API.
The 50 operations that already answer 200 with this key are deliberately not repeated here — see the full access request. The remaining 334 of the 406 catalog operations are not called by anything we run; the whole catalog, with every GET’s probe result, is the PWallet API Atlas.
