Hi, I suspect this is a long shot but I'm wondering if there's some way that I missed for me to generate a separate, read-only transaction key that I can use to make Transaction Details API calls.

I am writing some code to run unattended once a day and do a bookkeeping reconciliation between our Authorize.net transactions and our sales-tracking system. So far it's looking like this code I'm writing -- which only needs to be able to view past transaction details -- is going to have to store and use the same key that our live ecommerce sites are using.

I'd just as soon minimize the number of places where that fully-featured key is used and stored -- is this possible, or is there just one key per merchant account, always with full access?