Skip to Content
PredictorSDK

Corrected the documented `getEvent` call on the TypeScript and Go SDK pages

FixSDK

The "Client surfaces" table on the TypeScript and Go SDK reference pages documented GET /v1/events/{event_id} with the path parameter as a separate positional argument. It is a field on the request object. Copy-pasting either row did not compile:

pagepublishedactual
TypeScriptclient.getEvent(eventId, request)client.getEvent(request)
Goclient.GetEvent(ctx, eventID, request)client.GetEvent(ctx, request)

So the calls that work are client.getEvent({ eventId: "KXNBAGAME-26OCT20OKCSAS" }) and client.GetEvent(ctx, &predictorsdk.GetEventRequest{EventID: "KXNBAGAME-26OCT20OKCSAS"}).

The Python page was already correct and is unchanged. client.get_event(event_id, ...) is right there, because the generator hoists a path parameter to a positional argument in Python and keeps it on the request object in TypeScript and Go. The three tables describe three genuinely different call shapes; they are not supposed to match each other.

Only that one row was wrong — every other surface on all three pages already matched its generated client. The row was hand-written from the endpoint's shape rather than from the client, and nothing disagreed: the pages' runnable examples never call getEvent, and code inside an MDX fence is not typechecked by the docs build. Those tables are now verified against the generated clients and the OpenAPI spec on every CI run, so a table row that cannot compile fails the build instead of shipping.