Timestamp not rounded about currencylayer-api

Hi,

thanks for reaching out.

While the amount of time exchange rates are cached is identical for all Free & Basic Plan users, the caching periods are individual, depending on when requests are made.

Example: If your first API request on a particular day is made at 10:25:00 GMT your quotes will be cached for 60 minutes, until 11:25:00 GMT. The next caching period depends on when your next request is made, and so forth.

This enables us to deliver real-time data even for Free & Basic customers when requesting uncached (not within the 60 minutes after a request) quotes.

Please let us know here if there is anything else you need clarified, or write us an email at: [email protected]

Best regards,

David
Technical Support

[nii236]

Great, thanks for answering!

[nii236]

While I'm here, any chance the JSON api can also provide OHLC data instead of just bids and asks?

At this stage the currencylayer API delivers "midpoint" quotes only.

However, we are definitely interested in extending this spectrum to offer both bid/ask and OHLC data as well.

Be sure to follow @apilayernet on Twitter and allow us to send you service updates via the currencylayer service.

Have a nice day!

David

[nii236]

Further to the original issue, if the requests are cached every hour, and I write a script that makes a request every hour, will there not be a chance that I will get the same cached response (since my request might arrive 59:59:59 after the server receives my original request?

I want to make regular hourly checks, but if I have to account for exact one hour caching, I have to add drift into my script, which is undesirable.

Sorry for the slight delay.

The caching time does not amount to exactly 60 minutes, rather around 55 minutes. So you should be good to go using hourly checks.

Best regards,

Paul
Technical Support