You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working with the Etsy Open API v3, specifically handling payments, and I have two key concerns that I would like to clarify:
Retrieving a Complete List of Payments: Currently, I am uncertain whether I need to use both getShopPaymentByReceiptId and getPaymentAccountLedgerEntryPayments to fetch the entire list of payments, or if one of these endpoints alone would suffice. Could you provide some guidance on this?
Token Usage Limitation while Retrieving Payments: I have encountered an issue with the daily token usage limit when using the getShopPaymentByReceiptId endpoint. Although I can download 100 receipts in a single call, the associated payments take up many more calls (around 3K for 30 receipt calls). This imbalance is leading to inefficient usage of tokens. What would be the best approach to handle payment downloads without consuming thousands of tokens?
I would appreciate any insights or guidance to ensure an optimized way of handling these tasks. Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am working with the Etsy Open API v3, specifically handling payments, and I have two key concerns that I would like to clarify:
Retrieving a Complete List of Payments: Currently, I am uncertain whether I need to use both
getShopPaymentByReceiptId
andgetPaymentAccountLedgerEntryPayments
to fetch the entire list of payments, or if one of these endpoints alone would suffice. Could you provide some guidance on this?Token Usage Limitation while Retrieving Payments: I have encountered an issue with the daily token usage limit when using the
getShopPaymentByReceiptId
endpoint. Although I can download 100 receipts in a single call, the associated payments take up many more calls (around 3K for 30 receipt calls). This imbalance is leading to inefficient usage of tokens. What would be the best approach to handle payment downloads without consuming thousands of tokens?I would appreciate any insights or guidance to ensure an optimized way of handling these tasks. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions