WagerStreet · GSWallet API v1.0 · for Line Pros
The 72 operations Escazú Lion’s systems need enabled on our partner key, out of the 406 in the catalog. Every row below was found by scanning the code that calls the platform (235 call sites across 6 components), joined to what the key answered when each GET was probed on 2026-09-01. Nothing here is requested speculatively — each operation names the system that uses it and why. The grant request alone (sections B–D) is on its own page.
What we are asking. Please make sure the read-only partner key can reach every operation marked working (they do today — this is the list to keep intact), grant read access to the ones marked 403 blocked, grant write scope for the write operations our operator desks call, and confirm the ones we could not verify. The other 334 operations in the catalog are not requested.
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 remaining 334 operations in the 406-operation catalog are not called by anything we run and are not part of this request. The full catalog, with every GET’s probe result, is the PWallet API Atlas.