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
With the current IIssuingClient, there is a focus on getting/setting card information, but crucially, I think its missing these two operations for retrieving card transactions:
I have a work around currently whereby I am using reflection to get access to the underlying SdkAuthorization and ApiClient instances used by the client. This allows me to construct a manual call to ApiClient.Get<T>(path, auth, cancellationToken).
Interesting enough, maybe you could actually expose the ApiClient through AbstractClient as a property - this could mean people can write their own bespoke queries without having to wait for the SDK to catch up - e.g., the card transaction API calls are technically in beta, so you probably wouldn't support them through the SDK until they are GA, right? But if you exposed ApiClient as a property, people can write their own requests?
With the current
IIssuingClient
, there is a focus on getting/setting card information, but crucially, I think its missing these two operations for retrieving card transactions:https://api-reference.checkout.com/#tag/Transactions/paths/~1issuing~1transactions/get
https://api-reference.checkout.com/#tag/Transactions/paths/~1issuing~1transactions~1%7BtransactionId%7D/get
Is this on the backlog already, and if so, what is the ETA for this support?
The text was updated successfully, but these errors were encountered: