Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getTransactionInfo issue #5

Closed
bitog opened this issue Aug 4, 2020 · 4 comments
Closed

getTransactionInfo issue #5

bitog opened this issue Aug 4, 2020 · 4 comments

Comments

@bitog
Copy link

bitog commented Aug 4, 2020

Hi there,

I tried to pull a transaction using getTransactionInfo. I used a correct TXID however it is not returning anything to me. All I get is []. Any idea why that is happeing?

Thanks.

@mistal-distal
Copy link
Owner

Have you tried this on more than one transaction? In the past I've had intermittent issues with the API.

If you send along an example TXID, I'll give it a try.

@bitog
Copy link
Author

bitog commented Sep 4, 2020

Yes for sure.

Try the following TXID: CPEI48A1P31Y1N2SKCXGXKQSTF

@mistal-distal
Copy link
Owner

@bitog

Sorry about the wait. Couple of things to check here, the API key you're using might not have permissions to that API Call.

I shutoff all permissions on one of my API keys and recieved the following respone in the "Request" method of the CryptoPayments class:

error":"This API Key does not have permission to use that command!"

In Coinpayments go to Account > ApiKeys > Click "Edit Permissions" button for the relevant API key.

There's zero error handling for feedback for this API wrapper. Originally it was intended as a quick up start to using their API. I might spend some time updating and furthering the functionality.

@mistal-distal
Copy link
Owner

Should be fixed now, let me know if you have any further issues. There are breaking changes from the return of the API client, see the Readme, it now provides errors directly.

Previously the api would return a variable with fields, it now returns a python dictionary. Checking result['error'] should provide you more info if this latest commit does not immediately fix your issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants