Gap
Kalshi's spec defines GetCommunicationsID, which returns the logged-in user's communications identifier (used for the websocket/notifications channel). It's a standalone identity lookup under the /communications/* tag, distinct from the RFQ/Quote OTC-negotiation flow already tracked in issue #1229 ("Kalshi RFQ and Quote system"). It has no wrapper method anywhere.
Core
- Spec:
core/specs/kalshi/Kalshi.yaml:2225-2246 (operationId: GetCommunicationsID, response schema GetCommunicationsIDResponse at core/specs/kalshi/Kalshi.yaml:5120)
- Only present as an implicit-API descriptor entry:
core/src/exchanges/kalshi/api.ts:1876-1878. No wrapper method exists in core/src/exchanges/kalshi/index.ts or fetcher.ts — only reachable via untyped callApi('GetCommunicationsID').
TypeScript SDK
Missing — no reference to CommunicationsID or communications/id anywhere in sdks/typescript/pmxt/*.ts.
Python SDK
Missing — no reference to CommunicationsID/communications_id anywhere in sdks/python/pmxt/*.py.
Evidence
grep -n "GetCommunicationsID" core/specs/kalshi/*.yaml core/src/exchanges/kalshi/*.ts finds only the spec definition and the raw implicit-API descriptor entry. grep -rn "CommunicationsID\|communications/id" sdks/typescript/pmxt/*.ts sdks/python/pmxt/*.py returns no matches in either SDK.
Impact
Users have no typed/documented way to fetch the account's communications ID — only reachable via the untyped, undiscoverable callApi() escape hatch on the raw exchange instance (not available through the SDK client at all).
Found by automated Core-to-SDK surface coverage audit
Gap
Kalshi's spec defines
GetCommunicationsID, which returns the logged-in user's communications identifier (used for the websocket/notifications channel). It's a standalone identity lookup under the/communications/*tag, distinct from the RFQ/Quote OTC-negotiation flow already tracked in issue #1229 ("Kalshi RFQ and Quote system"). It has no wrapper method anywhere.Core
core/specs/kalshi/Kalshi.yaml:2225-2246(operationId: GetCommunicationsID, response schemaGetCommunicationsIDResponseatcore/specs/kalshi/Kalshi.yaml:5120)core/src/exchanges/kalshi/api.ts:1876-1878. No wrapper method exists incore/src/exchanges/kalshi/index.tsorfetcher.ts— only reachable via untypedcallApi('GetCommunicationsID').TypeScript SDK
Missing — no reference to
CommunicationsIDorcommunications/idanywhere insdks/typescript/pmxt/*.ts.Python SDK
Missing — no reference to
CommunicationsID/communications_idanywhere insdks/python/pmxt/*.py.Evidence
grep -n "GetCommunicationsID" core/specs/kalshi/*.yaml core/src/exchanges/kalshi/*.tsfinds only the spec definition and the raw implicit-API descriptor entry.grep -rn "CommunicationsID\|communications/id" sdks/typescript/pmxt/*.ts sdks/python/pmxt/*.pyreturns no matches in either SDK.Impact
Users have no typed/documented way to fetch the account's communications ID — only reachable via the untyped, undiscoverable
callApi()escape hatch on the raw exchange instance (not available through the SDK client at all).Found by automated Core-to-SDK surface coverage audit