Using Mondor API in consumer applications

by kristijn 24. September 2013 02:15

Today we celebrate the first 3rd party desktop application which is using our API services at back-end.

Here it is - a Windows 8 currency rates converter by Dmitry Kirsanov.

The application is free and ad-free, so you are welcome to install it for those special moments when you need to check “whether it’s just your app or our service”.

A few notes about this application and best practices for writing mobile and wide distribution applications:

  • Never use Mondor API directly from a mobile / desktop application.
    Always use your own back-end, which is connecting to Mondor API. There are few reasons for that - to not overload our servers and to not expose the access key.

    While we are serving thousands of websites and server applications with millions of requests per day, they are relatively easy to handle - the same IP address, the same web services / WCF / WebAPI client, the same connectivity. Mobile and desktop applications usually do not have very good connection, may drop it in the middle, may be slow to respond and behave in the way that it may create problems for the service. When the client creates problems, the access key may be suspended. When the access key is suspended, your mobile application stops functioning.

    The idea of not exposing your access key is quite obvious - when we see that someone else is trying to use your key, the key is disabled and you may request new one, unless it was you who published it. Nevertheless, it means downtime for your service.
  • When connecting from your custom back-end (a proxy between your clients and our API) try to use WebAPI or WCF, instead of classic XML Web Services. You will see that traffic and response times are better.
  • Contact us if you have questions - our support is always willing to assist, especially if it helps to prevent problems in the future.
  • Ensure that your WCF client supports data compression. This will help you to make your applications way more responsive.
  • Use asynchronous calls for better responsiveness, even between your application and your service.
  • Cache data, it’s better to save traffic than server memory.


The mentioned desktop application, as well as its Windows Phone counterpart, are using their own servers with data compression and authentication mechanisms, and that means, that even if our service would be inaccessible, the application still works. Besides, if the application service doesn’t work, it doesn’t mean that API is down. Such independence provides a better environment for both yours and our customers.

Ensuring business continuity through upgrade keys and subscription

by kristijn 10. May 2013 18:59

This article is based on a post from now discontinued support forum. It is still available here.

Mondor’s Currency Rates Web API has one unique feature – rechargeable access keys. You can buy them as any other keys, and sometimes they are cheaper, but they can be used for a sole purpose of recharging another key of the same type.

Imagine, that you have successfully applied our currency conversion service in your application. Now your application is installed in many different places and your users expect it to work 24/7. Redeploying application just because you have to replace API key is a bad option.

Recharge key allows you to prolong the life of existing key without touching your application. And here is how it works:


New feature: Access Subscription

by kristijn 29. April 2013 08:57

To ensure uninterruptable service to our corporate customers, as well as anyone who doesn’t want to deal with access control, we introduce new, subscription based access code provisioning.

Now you can get your automatically renewing access code, which will renew every 6 months for $50, which makes this code the most affordable one, as the standard annual access code’s price at this moment is $120.

You will be notified 2 weeks before the charge by RegNow, so you may cancel your subscription any time.

You can acquire such key by visiting the link below:

Note that link is different than for other keys, to avoid accidental purchase.

Backup Servers

by kristijn 27. February 2013 05:38

To minimize the downtime we’ve established a backup server for the currency rates API. Should you experience any problems with the main URL, use this server name instead:

Please note, that backup servers will only be available for keys with expiration date, such as Monthly, Annual, 6 months and Quarter. Keys with the maximum number of API calls or limited by maximum number of API calls per day, should only be served by the main service.

Web API access

by kristijn 18. February 2013 04:41

Finally, we’ve enabled the Web API access, which could be used to simplify access to our currency rates API service from JavaScript or anything else.

Consider the following URL:

This simple URL contains 6 parts:

  1. Path to conversion service, which is
  2. Your access key
  3. Base currency
  4. Target currency
  5. Amount of base currency to convert (OPTIONAL, default is 1)
  6. Date of conversion rate (OPTIONAL, default is today, format is DDMMYYYY)

You can also use the HTTPS instead of HTTP, so that your connection would be protected by 2048 bit SSL. In that case your query would look like

(in this example we are querying the current rate for 1 unit of EUR).



Page List

Month List