Skip to content

spec-drift/kalshi: Fill schema — side + action deprecated (May 14 2026); outcome_side, book_side missing #1188

Closed as duplicate

Description

@realfishsam

Summary

The Kalshi v2 API deprecated side and action on the Fill schema (same May 14, 2026 deadline as Trade) and added outcome_side and book_side as replacements. The PMXT spec (core/specs/kalshi/Kalshi.yaml v3.7.0) retains the deprecated fields and does not include the replacements.

API changes — Fill schema

Deprecated (removal deadline May 14, 2026)

  • side — was "yes" or "no"
  • action — was "buy" or "sell"

Added

Field Type Description
outcome_side string "yes" or "no" — which outcome was filled
book_side string "bid" or "ask" — which side of the book was filled

Impact

Any normalizer code reading side or action from fill data may receive null/undefined for fills settled after the deprecation deadline. The new fields are unavailable for P&L or trade direction display.

Spec file

core/specs/kalshi/Kalshi.yaml — Fill schema needs side and action marked deprecated and the two new fields added.

See also: companion issue for Trade schema deprecations (#1187).

Activity

  1. realfishsam commented on Jun 24, 2026

    @realfishsam
    ContributorAuthor

    Triage: removed P1: high because the Kalshi deprecation deadline (May 14 2026) has now passed — today is June 24 2026, 41 days after the deadline. The side + action fields have been removed from Fill responses and outcome_side / book_side are now required. Fill data is silently wrong or broken in production. Added P0: critical instead.


    Generated by Claude Code

  2. realfishsam commented on Aug 4, 2026

    @realfishsam
    ContributorAuthor

    Triage: removed P0: critical because, unlike the repo's other P0 spec-drift issues (which describe complete request failures or fully broken data), this one's impact is side/action becoming null/undefined on fills — a data-completeness gap affecting P&L/trade-direction display, not a crash or full outage. Added P1: high instead (breaking API change needed, but not production-down).


    Generated by Claude Code

  3. realfishsam commented on Sep 4, 2026

    @realfishsam
    ContributorAuthor

    Closing as duplicate of #514. Same underlying finding: Kalshi's outcome_side/book_side field migration replacing legacy direction-style fields on the Order/Fill/Trade family in core/specs/kalshi/Kalshi.yaml. The Fill-specific detail from this issue (deprecated side/action fields, May 14 2026 deadline) has been copied over to #514 as a comment so it isn't lost.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions