What Is Elite Dangerous Market Connector?

Elite Dangerous Market Connector ("EDMC") is a third-party application for use with Frontier Developments' game "Elite Dangerous". Its purpose is to facilitate supplying certain game data to, and in some cases retrieving it from, a number of websites and other tools.

To achieve this it utilises the Journal Files written by the game when played on a PC. It also makes use of Frontier's Companion API ("Frontier's CAPI"), accessible once you've authorised this application.

EDMC has a plugin system which many other developers have made use of to extend its functionality.

Find out more on the EDMC Wiki.

NB: This application is of no use with a Console game account. We now test against, and package with Python 3.9.8. As a consequence of this we no longer support Windows 7, due to Python 3.9.x itself not supporting Windows 7.

As has become routine now, various anti-virus software are reporting a false positive on our installer and/or files it contains. I've pre-emptively uploaded the installer to VirusTotal if you want to check what it's saying. Please see our Troubleshooting/AV-false-positives FAQ for further information.

Release 5.2.2

This release adds one new feature and addresses some bugs. We've also updated to using Python 3.9.8.

• Windows now has "minimize to system tray" support.
  • The system tray icon will always be present. – There is a new option on the Settings > Appearance tab –
    Minimize to system tray.
  • When this new option is active, minimizing the application will also
    hide the taskbar icon.
  • When the new option is not active, the application will minimize to the
    taskbar as normal.

Bug Fixes​

​

• If a CAPI query failed in such a way that no requests.Response object
  was made available we attempted to blindly dump the non-existent object. We now check that it actually exists, and log the specifics of the exception.
• A user experienced the game writing a NavRoute.json file without a
  Route array, which caused the application to attempt sending a badly formed navroute message to EDDN. That message was then remembered and constantly retried.
  • We now sanity check the NavRoute.json contents to be sure there is a
    Route array, even if it is empty. If it's not present no attempt to send the EDDN message will be made.
    If this scenario occurs the user will see a status line message No 'Route' array in NavRoute.json contents.
  • For any EDDN message that receives a 400 status back we will drop it
    from the replay log.