I am confused on the maximum number of operations that can be batched in a single call to Batch Create Orders V2 / Batch Cancel Orders V2. The v1 version of v2 had a per-tier definition and Advanced was 20 per batch. I don't see such a definition any more.
The OpenAPI documentation says, "The maximum batch size scales with your tier’s write budget — see Rate Limits and Tiers.", but I see no reference to the max batch size in https://docs.kalshi.com/getting_started/rate_limits.
Is there just no limit now other than the token cost?
I am confused on the maximum number of operations that can be batched in a single call to Batch Create Orders V2 / Batch Cancel Orders V2. The v1 version of v2 had a per-tier definition and Advanced was 20 per batch. I don't see such a definition any more.
The OpenAPI documentation says, "The maximum batch size scales with your tier’s write budget — see Rate Limits and Tiers.", but I see no reference to the max batch size in https://docs.kalshi.com/getting_started/rate_limits.
Is there just no limit now other than the token cost?
each order in the batch counts as much as a single order in a non-batch...so yeah it's pretty much token cost limited
each order in the batch counts as much as a single order in a non-batch...so yeah it's pretty much token cost limited
What do you mean seconds?
What do you mean seconds?
They'd all apply to the rate limit the moment they hit the server.
They'd all apply to the rate limit the moment they hit the server.
Rate limit is tokens/second. This is orthogonal to how many operations can be placed into a single batch. Formerly, v1 of v2, there was a limit of 20 operations per batch.
Rate limit is tokens/second. This is orthogonal to how many operations can be placed into a single batch. Formerly, v1 of v2, there was a limit of 20 operations per batch.
Yeah, but the "seconds" are grouped into buckets. So if you exceed your total token limit in a single batch I'm assuming it'll either be rejected entirely or will only place the first few until you hit your rate limit.
Yeah, but the "seconds" are grouped into buckets. So if you exceed your total token limit in a single batch I'm assuming it'll either be rejected entirely or will only place the first few until you hit your rate limit.
`Batch endpoints don’t save tokens` covers it pretty well:
https://docs.kalshi.com/getting_started/rate_limits
`Batch endpoints don’t save tokens` covers it pretty well:
https://docs.kalshi.com/getting_started/rate_limits
The entire batch would be rejected.
The entire batch would be rejected.
I get that the entire batch should be rejected if it would exceed the rate limit. I am skeptical that this is what happens. I am asking if there is still a maximum number of operations permitted per batch.
I get that the entire batch should be rejected if it would exceed the rate limit. I am skeptical that this is what happens. I am asking if there is still a maximum number of operations permitted per batch.
You think it's allowing them through? Could test it by placing orders no one will take.
You think it's allowing them through? Could test it by placing orders no one will take.
This is one of the reasons that I am asking. My logs are showing inconsistent states now that I have migrated from v1 of v2 to v2 of v2. Were you sending multiple operations per batch using the v1 endpoint?
This is one of the reasons that I am asking. My logs are showing inconsistent states now that I have migrated from v1 of v2 to v2 of v2. Were you sending multiple operations per batch using the v1 endpoint?
Max I was placing 2 orders per batch via v1 and then v2. Migrated once the token costs made v1 hit rate limits.
Max I was placing 2 orders per batch via v1 and then v2. Migrated once the token costs made v1 hit rate limits.
v1 API states `The maximum batch size scales with your tier’s write budget`
v2 says the same `The maximum batch size scales with your tier’s write budget`
v1 API states `The maximum batch size scales with your tier’s write budget`
v2 says the same `The maximum batch size scales with your tier’s write budget`
I am talking about an older restriction on v1.
I am talking about an older restriction on v1.
Yes, I am aware of what the current documentation claims.
Yes, I am aware of what the current documentation claims.
Batch deletes are cheaper:
```
{
"cost": 2,
"method": "DELETE",
"path": "/trade-api/v2/portfolio/events/orders/batched"
},
```
Batch deletes are cheaper:
```
{
"cost": 2,
"method": "DELETE",
"path": "/trade-api/v2/portfolio/events/orders/batched"
},
```
and batch orders are more expensive at the base level
```
{
"cost": 20,
"method": "POST",
"path": "/trade-api/v2/portfolio/orders/batched"
}
```
and batch orders are more expensive at the base level
```
{
"cost": 20,
"method": "POST",
"path": "/trade-api/v2/portfolio/orders/batched"
}
```
via: https://docs.kalshi.com/api-reference/account/list-non-default-endpoint-costs?playground=open#list-non-default-endpoint-costs
via: https://docs.kalshi.com/api-reference/account/list-non-default-endpoint-costs?playground=open#list-non-default-endpoint-costs
yes
yes
That is not the question I am asking.
That is not the question I am asking.