Skip to content

Spec drift 2026-06-22: openapi 3.21.0 → 3.21.0 #458

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: b2452ce646328543c98e69262cb4420b7b0a024eb545a47bc646168ac6e474ba
  • specs/asyncapi.yaml: 79f743934c94ab9d0ccbffc08e99f8f8dbacab6ca82c439fbcc68aba8b31dd88
  • specs/perps_openapi.yaml: 4077a0d5684f145f2c418c165ea8fc507507cab3018509a9b3f8fe43a017a2e2
  • specs/perps_asyncapi.yaml: 1dd279561bc2e4c1aacbfc5723fe41dfc4a24f9c64b1b39ec2be8f95d0945b15
  • specs/perps_scm_openapi.yaml: 2d9ab3a55ee0775a70b493ea8acb6e06dffdad2c11619ac9d2351a4a89923e68

Reproduce locally and verify the same hashes before generating models.

Perps (margin) specs

  • perps OpenAPI changed: false
  • 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.21.03.21.0
  • Endpoints: 90 → 89 paths

Added endpoints

(none)

Removed endpoints

/portfolio/orders/{order_id}/amend

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