Kalshi API
DELETE /trade-api/v2/portfolio/orders/{id} endpoint removal
Deprecated, no dateSubscribe to Kalshi APIShare
Kalshi API announced on June 18, 2026, that the endpoint DELETE /trade-api/v2/portfolio/orders/{id} is deprecated without a shutdown date. Kalshi API noted that legacy portfolio orders mutation endpoints are slated for deprecation between June 18 and June 25. Calls to this endpoint will eventually fail once the removal takes effect.
Calls it hits
DELETE /trade-api/v2/portfolio/orders/{id}
What to use instead of these calls
Use DELETE /trade-api/v2/portfolio/events/orders/{order_id} (Cancel Order V2) instead.
In Kalshi API's words
Legacy /portfolio/orders mutation endpoints will be deprecated sometime between June 18 and June 25.
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 DELETE /trade-api/v2/portfolio/orders/{id} 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 9
-
GET /trade-api/v2/communications/quotesBehaviour change Stopped working -
GET /trade-api/v2/exchange/announcementsEndpoint removal Stopped working -
PUT /trade-api/v2/multivariate_event_collections/{id}/lookupEndpoint removal Stopped working -
No date
DELETE /trade-api/v2/portfolio/orders/batchedEndpoint removal Deprecated, no date -
No date
GET /trade-api/v2/communications/quotes/{id}Endpoint removal Deprecated, no date -
No date
POST /trade-api/v2/portfolio/ordersEndpoint removal Deprecated, no date -
No date
POST /trade-api/v2/portfolio/orders/{id}/amendEndpoint removal Deprecated, no date -
No date
POST /trade-api/v2/portfolio/orders/{id}/decreaseEndpoint removal Deprecated, no date -
No date
POST /trade-api/v2/portfolio/orders/batchedEndpoint 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.