Release EDDN - Elite Dangerous Data Network. Trading tools sharing info in an unified way.

Status
Thread Closed: Not open for further replies.

wolverine2710

Tutorial & Guide Writer
wolverine2710
Kraszus said:
Thank you for this Wolverine :D
Click to expand...

Thanks for your kind words.

What is the point of having a LEGAL api and a dedicated and spezialised sub-forum if nobody knows about ;-> I've also updated most of the OP's of my other relevant threads witht the same "api and sub-forum" info. Perhaps it gets noticed and more commanders are starting to use the api and flood EDDN with much needed data. See also the "Monitoring the usage of api-tools using EDDN as an indicator" thread. Feed me seymour, feed me.
 

wolverine2710

Tutorial & Guide Writer
wolverine2710
Now that the api tools are LEGAL more and more commandes are starting to share their internal tools and proof and concepts for accessing the api. One novel approach is by jgm in the thread "Accessing the API using Curl. Also the thread "Existing API resources" has some very nice programs/POC's in it. Also of interest "API and Powershell - Questions". It contains very good information and solutions. I'm planning/hoping to create an EDCodex entry for it and/or a thread in the api subforum which gives an overview of them all. I'm dreaming of POC's like jgm's one for as much programming languages and operating systems as possible.
 
Last edited:

Vaerah

V
wolverine2710 said:
Updated OP on Saturday the 23th of January 2016.

I've updated the OP. It was LONG overdue. Also added the following to it.

Brilliant news: On the 5th of January 2016, Zac Antonaci -Head of Community Management of FD- wrote in the "Open Letter to Frontier Developments" thread that usage of the iPhone companion app api is LEGAL. Source. Which makes the usage of tools which use this api like EDMC, EDAPI and EDCE LEGAL. Other great news: On the 18th of January 2016, Brett C. -Community Assistant/Manager of FD- created the "Elite Dangerous->Gameplay and Features->Player Tools & API Development" subforum. Its an excellent place for checking out new and existing tools. The EDCodex thread is also there.
Click to expand...


Sadly this good news is more than nulled by the fact that since Horizons came out, no valid API keys are being generated for new users any more. Please look at EDMarketConnector issues for details. Basically every new player who did not purchase the original game is not going to be able to send his market data to the very services that were made to use this neat API. As elder players eventually stop playing, data feeds will become more and more less frequent.
 

jamesremuscat

J
Vaerah said:
Sadly this good news is more than nulled by the fact that since Horizons came out, no valid API keys are being generated for new users any more. Please look at EDMarketConnector issues for details. Basically every new player who did not purchase the original game is not going to be able to send his market data to the very services that were made to use this neat API. As elder players eventually stop playing, data feeds will become more and more less frequent.
Click to expand...

I'd be surprised if this was a permanent situation - feels more like a bug. I've sent a PM asking for clarification since (as per the issue you link) it doesn't seem that support fully understand what they were being asked.
 

Andargor

Andargor
Vaerah said:
Sadly this good news is more than nulled by the fact that since Horizons came out, no valid API keys are being generated for new users any more. Please look at EDMarketConnector issues for details. Basically every new player who did not purchase the original game is not going to be able to send his market data to the very services that were made to use this neat API. As elder players eventually stop playing, data feeds will become more and more less frequent.
Click to expand...

If they try to use the iOS Elite Dangerous Companion app, you are saying that it does not work for new players? Then that is a bug which should be reported, since the app is officially supported. If the app works, then the API for everything else should work.

EDIT: From the bug thread, it seems that's what they are doing, but it is low on FD's priority list.
 
Last edited:

Askarr

A
EDDN Archive V1 released

For anyone using the EDDN Archive on AWS, I'm pleased to release V1, finally get it out of beta, and give it a home on Github where issues can be reported without clogging up threads here on Frontier. There are quite a few significant bug fixes and changes for clients, so I'll be leaving the existing beta endpoint up for a couple of months. Unless anyone speaks up to indicate otherwise, I'll then shut the beta endpoint down with an expectation that everyone's migrated across.

Drop me a PM if updated access is desired, or open a Github issue if you encounter any significant problems.
 

Askarr

A
Anyone else having trouble with EDDN? I've started a couple of subscribers (code that I know has worked for months, different networking regions) and they're almost never getting any messages, though I can see that active ones e.g. edbb.io are regularly getting data. Thanks in advance if anyone gets a chance to look into it.
 

AnthorNet

AnthorNet
Askarr said:
Anyone else having trouble with EDDN? I've started a couple of subscribers (code that I know has worked for months, different networking regions) and they're almost never getting any messages, though I can see that active ones e.g. edbb.io are regularly getting data. Thanks in advance if anyone gets a chance to look into it.
Click to expand...

I just restarted the relay as someone else as pointed that the monitor was receiving no messages too.
Tell me if that's working.
 

maddavo

maddavo
There is a tool "Elite: Dangerous Assistant v0.95" that is publishing some data to EDDN. I can't find that tool on edcodex . Can someone point me to a thread for that tool or the @ of the author?
 

Otis B.

Otis B.
in preparation for E: D 2.2 EDDN now supports some new schemas for commodities, modules and ships. The new schemas, the rationale for the change, and example messages are described here.

If you use an app or site that sends or receives data over EDDN you should hopefully see no immediate difference after the switch, except that new commodities/modules/ships in 2.2 should be handled more gracefully than they were in 2.1.
If you author an app or site that sends or receives data over EDDN please see Implications for senders and Implications for listeners for what this means to you.

FYI EDMC will start sending data to EDDN using the new schemas some time before 2.2 is released.
 
Last edited:

Andargor

Andargor
Otis B. said:
in preparation for E: D 2.2 EDDN now supports some new schemas for commodities, modules and ships. The new schemas, the rationale for the change, and example messages are described here.

If you use an app or site that sends or receives data over EDDN you should hopefully see no immediate difference after the switch, except that new commodities/modules/ships in 2.2 should be handled more gracefully than they were in 2.1.
If you author an app or site that sends or receives data over EDDN please see Implications for senders and Implications for listeners for what this means to you.

FYI EDMC will start sending data to EDDN using the new schemas some time before 2.2 is released.
Click to expand...

I've mentioned this on Discord, but I've been getting 400 errors when submitting from EDCE using v2 schema. Has something changed? This follows a fix for EDCE where demandBracket and stockBracket were sometimes blank in the API response.

EDIT: Nevermind, the blank entries were causing errors elsewhere in my code, breaking against the schema. Reading the validation error helps :D
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom