Skip to content

Spec drift 2026-07-06: openapi 3.23.0 → 3.23.0 #470

Description

@github-actions

Spec drift detected

Upstream specs changed since the last sync. This workflow runs with
contents: read only — it does NOT push a branch or open a PR.

To resolve: locally run uv run python scripts/sync_spec.py +
uv run python scripts/generate.py, audit the diff (including
kalshi/_generated/models.py), and open a PR whose body contains
Closes #<this issue number> so this issue auto-closes on merge.

Spec checksums (sha256 of fetched upstream content)

  • specs/openapi.yaml: 557683c9375b6ab29a68a6cd0640ac18ee0236a529557207b1fa2f34955b4cbe
  • specs/asyncapi.yaml: 00858d5a892eb7066a8da247660622721e8ee80bfdd89b1b9a24278c15d7d421
  • specs/perps_openapi.yaml: 5f4753c1a7dff0513527a1dfea7a7d5083d9f071a4f90248397f0563f71572de
  • specs/perps_asyncapi.yaml: 1dd279561bc2e4c1aacbfc5723fe41dfc4a24f9c64b1b39ec2be8f95d0945b15
  • specs/perps_scm_openapi.yaml: a5e4bda9b7125868e49e276c504a5a5741c90396940168226ac3148191e39f9c

Reproduce locally and verify the same hashes before generating models.

Perps (margin) specs

  • perps OpenAPI changed: true
  • perps AsyncAPI changed: false
  • perps SCM/Klear changed: false

A perps-spec change reds the perps contract-drift suites in
tests/test_contracts.py (the TestPerps*Drift classes). Re-vendor with
scripts/sync_spec.py and reconcile the perps models/maps under kalshi/perps/.

OpenAPI

  • Version: 3.23.03.23.0
  • Endpoints: 91 → 90 paths

Added endpoints

(none)

Removed endpoints

/exchange/announcements

AsyncAPI

  • Channels: 14 → 14

Added channels

(none)

Removed channels

(none)

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec-driftUpstream OpenAPI/AsyncAPI spec changed since last sync

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions