History not working right - possible date formatting issue

[wayne47git]

I'm messing with a test program to get account history.
If I use
await a.get_history(session, start_date=date(2026, 2, 1)
I do not seem to get any transactions from 2/1 - 2/6. I fo get the last 20 transactions on the account. If I change to
await a.get_history(session, start_date=date(2026, 2, 1), end_date=(2026, 2, 9))
I get an error:

site-packages/tastytrade/utils.py", line 264, in validate_response
    |     raise TastytradeError(message)
    | tastytrade.utils.TastytradeError: end-date: is invalid

Changing to (2026, 2, 10) does not error but also does not get the early Feb transactions, it returns the transactions from 02/09 through 02/26, which is clearly incorrect.

[Graeme22]

Seems like maybe you're passing a tuple instead of a date?

[wayne47git]

From the docs under accounts:

history = await account.get_history(session, start_date=date(2024, 1, 1))
print(history[-1])

Is this out of date?

[wayne47git]

OK, yes, I was missing the date() on the end date.

But, the code I was starting with still fails to get the beginning transactions in Feb:

history = await a.get_history(session, start_date=date(2026, 1, 1))

[Graeme22]

Working fine for me. Could you provide code that reproduces this? Since your example wasn't valid.

[wayne47git]

OK, here's a clip of the actual code. It returns 20 transactions in Feb for PLTR and nothing in Jan.

I run with:
orders.py | grep TOP | grep PLTR | grep <account #>

Other accounts/symbols that are less than 20 transactions work fine, returning all since beginning of year.

async def show_monthly():
    global g_month
    accounts = await Account.get(session)
    for a in accounts:
        history = await a.get_history(session, start_date=date(2026, 1, 1))
        for h in history:
            console.log('TOP', h.account_number, h.quantity, h.price, h.net_value, h.description, h.transaction_date)
            l_match = False

[Graeme22]

I have a feeling this isn't an SDK issue, could you see what happens if you run the same request in Postman?

https://www.postman.com/tastytradeapi/tastytrade-api/overview

[wayne47git]

Not sure exactly what that is?

[Graeme22]

Not sure exactly what that is?

It's Tasty's official API sandbox that lets you test requests. This is what the SDK is doing behind the scenes. Specifically you'd want this endpoint: https://www.postman.com/tastytradeapi/tastytrade-api/request/y2pzbd1/account-transactions?sideView=agentMode&tab=overview

[wayne47git]

Is this official Tasty? I'm not real comfortable uploading my credentials to some random site.

[Graeme22]

Is this official Tasty? I'm not real comfortable uploading my credentials to some random site.

Yes, it's in their docs: https://developer.tastytrade.com/sdk/

[wayne47git]

I guess it's broken.

The first thing you'll want to do is run the Login request.

Link fails

[wayne47git]

And I can't figure out where to put my Secret or Refresh

[Graeme22]

Can you try running this script to get your token:

session = Session('secret', 'refresh')
await session._refresh()
print(session.session_token)

Then running this command in a terminal:

$ curl "https://api.tastyworks.com/accounts/{YOUR_ACCOUNT}/transactions?per-page=250&page-offset=0&sort=Desc&start-date=2026-02-01&end-date=2026-02-24" \
                                                     -H "accept: application/json" \
                                                     -H "content-type: application/json" \
                                                     -H "accept-version: 20251101" \
                                                     -H "authorization: Bearer {YOUR_TOKEN}"

making sure to fill in the account number and token parts?

[wayne47git]

Same problem.
But I noticed that 250 in there. So I changed it to something reasonable (5000) and got this error:
{"error":{"code":"validation_error","message":"Request validation failed","errors":[{"domain":"per-page","reason":"does not have a valid value"}]}}

It appears that the limit is 2000 as 2001 generates the error
Not sure what the limit is or why it's so small.

Is there any way I can determine that I've reached the max? Am I going to have to do this on a super-short-term basis?

[Graeme22]

Same problem. But I noticed that 250 in there. So I changed it to something reasonable (5000) and got this error: {"error":{"code":"validation_error","message":"Request validation failed","errors":[{"domain":"per-page","reason":"does not have a valid value"}]}}

In that case, you should reach out to Tasty support, show them the command you're running and the output you're getting (with the 250, not working with 5000 is expected)

It appears that the limit is 2000 as 2001 generates the error Not sure what the limit is or why it's so small.

Is there any way I can determine that I've reached the max? Am I going to have to do this on a super-short-term basis?

Not sure why you consider 2000 "small" haha! No you don't have to stick to short term, the endpoint is paginated, you can fetch all pages by passing page_offset=None: https://tastyworks-api.readthedocs.io/en/latest/api/account.html#tastytrade.account.Account.get_history.page_offset