Okapi Okapi
Add to GitHub

POST /trade-api/v2/portfolio/orders/batched → endpoint removal

Kalshi API

Deprecated, no date

Kalshi announced on June 18, 2026, that the POST /trade-api/v2/portfolio/orders/batched endpoint is deprecated without a shutdown date. The provider noted that legacy endpoints will be deprecated sometime between June 18 and June 25. Once shut down, requests to this endpoint fail.

Calls it hits

  • POST /trade-api/v2/portfolio/orders/batched

What to use instead of these calls

Use POST /trade-api/v2/portfolio/events/orders/batched (Batch Create Orders V2) instead.

In Kalshi API's words

Legacy /portfolio/orders mutation endpoints will be deprecated sometime between June 18 and June 25.

Kalshi API, Announcement

Facts

API
Kalshi API api.elections.kalshi.com
Kind
Endpoint removal
Announced
June 18, 2026
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Kalshi API's own pages

Questions

When does this change take effect?

Kalshi API deprecated POST /trade-api/v2/portfolio/orders/batched without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Kalshi API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

More from Kalshi API 6

  1. GET /trade-api/v2/communications/quotesBehaviour change Stopped working
  2. GET /trade-api/v2/exchange/announcementsEndpoint removal Stopped working
  3. PUT /trade-api/v2/multivariate_event_collections/{}/lookupEndpoint removal Stopped working
  4. No date DELETE /trade-api/v2/portfolio/orders/{}Endpoint removal Deprecated, no date
  5. No date DELETE /trade-api/v2/portfolio/orders/batchedEndpoint removal Deprecated, no date
  6. No date GET /trade-api/v2/communications/quotes/{}Endpoint removal Deprecated, no date

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub