I'm probably a unique use case, but I'd like to use this to "fix" the exchange rates portion of Apple's currency converter dashboard widget, and I want it to work even on very old OS's. That means I can't use TLS 1.2, and the root certs are often out of date anyway.
I'm currently using exchangeratesapi.io, which doesn't support HTTP either, but does support TLS 1.0, so it kind of works. However, outdated root certs mean I need to instruct users to manually install exchangeratesapi's certificate, which I'd rather not do.
I was looking for this exact thing a few weeks ago, and couldn't believe how difficult it was to find a decent, free API for crypto exchange rates (I just wanted to write a little script that tracked my investments, nothing huge.)
(Also, I'm the founder of ReadMe; we do API docs... if you want to use us, my emails in my bio :) )
```
var requestURL = 'https://api.exchangerate.host/latest';
var request = new XMLHttpRequest();
request.open('GET', requestURL);
request.responseType = 'json';
Your website looks good. The examples in several languages is also a nice touch (expected from API documentation).
I do have plenty of questions though.
Does this service get historical rates from its sources in real time or does it store those in its own local database?
How long will this service be free for? What’s the business model that’s being thought about?
What kind of rate limiting, if any, is used so that a developer who uses these APIs doesn’t have their app go down because someone else is hammering the server with a lot of requests?
> Does this service get historical rates from its sources in real time or does it store those in its own local database?
Historical data are stored and synchronized at regular intervals in the local db.
> How long will this service be free for? What’s the business model that’s being thought about?
I was looking for stable service and i did not find any,
that would have satisfied my needs, so i decidide create myself.
Current features will be as free in the future as they are now.
> What kind of rate limiting, if any, is used so that a developer who uses these APIs doesn’t have their app go down because someone else is hammering the server with a lot of requests?
Yes, there are rate limit, currently 300 per minute, you can see it in the response header.
Very slick site! In a previous life I worked in the crypto transaction tracing space, I ended up building my own tool to do what your API does, but this is much more polished than my tool haha.
Very curious about the front-end! I'd get many more side-projects out the door if I understood the path to get a polished landing page / front-end like yours!
How does this compare to https://www.sendwyre.com/?
Seems like you have multiple features including some conversion so interested in hearing about the differences.
I like the illustration of the people building the application a lot. Is there a name for this type of image?
Say I'd like to hire someone to make one of these images, what would I be searching for?
I'm probably a unique use case, but I'd like to use this to "fix" the exchange rates portion of Apple's currency converter dashboard widget, and I want it to work even on very old OS's. That means I can't use TLS 1.2, and the root certs are often out of date anyway.
I'm currently using exchangeratesapi.io, which doesn't support HTTP either, but does support TLS 1.0, so it kind of works. However, outdated root certs mean I need to instruct users to manually install exchangeratesapi's certificate, which I'd rather not do.