Jump to content

"unable to retrieve transaction(s)" from Ripple Data API v2 for some date ranges


FractalByte

Recommended Posts

Hi there, I have been trying to use the Ripple Data API v2 to get transaction data by date. I've been working backwards but the API is returning the error (in the title) for dates before 2017-04-16. The url I am using is http://data.ripple.com/v2/transactions/?start=2017-04-16&end=2017-04-17&marker=&format=json&limit=100&type=Payment

It does work for 2017-04-17 to 2017-08-31 and dates in 2014. I've tried it without specifying format or payment type but it hasn't made any difference

Any ideas what I could do?

Link to comment
Share on other sites

4 hours ago, FractalByte said:

Hi there, I have been trying to use the Ripple Data API v2 to get transaction data by date. I've been working backwards but the API is returning the error (in the title) for dates before 2017-04-16. The url I am using is http://data.ripple.com/v2/transactions/?start=2017-04-16&end=2017-04-17&marker=&format=json&limit=100&type=Payment

It does work for 2017-04-17 to 2017-08-31 and dates in 2014. I've tried it without specifying format or payment type but it hasn't made any difference

Any ideas what I could do?

Dates need to be in another format, yyyy-mm-ddThh:mm:ssZ

https://ripple.com/build/data-api-v2/#timestamps

Edit: Hmm, doesn't work for me regardless of timestamp format, even removing other optional variables...

Edited by Guest
Link to comment
Share on other sites

7 hours ago, FractalByte said:

Hi there, I have been trying to use the Ripple Data API v2 to get transaction data by date. I've been working backwards but the API is returning the error (in the title) for dates before 2017-04-16. The url I am using is http://data.ripple.com/v2/transactions/?start=2017-04-16&end=2017-04-17&marker=&format=json&limit=100&type=Payment

It does work for 2017-04-17 to 2017-08-31 and dates in 2014. I've tried it without specifying format or payment type but it hasn't made any difference

Any ideas what I could do?

Why do you specify &format? Oo. Api v2 is glitchy for transactions. It doesn't work for txs after March '17. I raised the similar issue a couple of days back. You can, however access v2/payments without issues (if you need payments only).


A workaround - specify &binary = true to retrieve the hashes for the txs in your timeframe from /transactions endpoint. You will have to retrieve the json format for each txhash then manually (via /transactions/[yourhash here] or rpc calls to rippled)


But be ready that it will throw error when you specify the type other than OfferCreate/Cancel. 

Edited by Graine
grammar
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...