Dear players,
first off, a couple of words about this post: We have been monitoring feedback in the communities about how 3rd party tools interact with OGame. In order to work together on some of these issues we want to try out this new type of "Dev Post". To accommodate all language communities these posts will be made in the Origin Board and in english only. Feel free to direct any potentially interested players / developers to this post.
Now, for the good stuff:
As you have probably heard, with OGame 6.0 changes to the display of Combat Reports (CR) are being made. This has caused concerns about different 3rd party tools breaking because of these changes. To address these concerns and for a more stable solution, we have fleshed out the following:
We wish to offer players the possibility to share combat reports with 3rd party tools in a more simplified and safe manner.
For this we are currently planning a new API that will allow 3rd party developers to directly request combat reports from our servers. In an upcoming snapshot of version 6.0 players will find a new button on their combat reports that allows them to copy a Combat ID to their clipboard (CR_ID).
Using this CR_ID and an application key (API_KEY) issued to 3rd party developers by OGame, tools will be able to directly request the combat information from our server in a machine readable format for storage and processing on their own servers. We *will* be monitoring requests to the API *very* closely.
Please note: The player himself stays in control of which CR_IDs is shared, it will not be possible to retrieve CRs without the ID the player provides.
Our reasonings for this move are the following:
We are currently still fleshing out the format of the key and the data to be returned by the API, as well as technical formalities that need to be taken care of before we open up this API to the communities.
Additionally, we are working on procedures for requesting API_KEYs from OGame. Most likely, Test Servers will have a global API_KEY for testing purpose, live server can only be accessed with a personalized API_KEY (per tool/website/3rd party developer).
Depending on the acceptance of "API verified" combat reports, we may extend this new API to other pieces of game information in the future, for example alliance or per-user information.
Attached is a mock screen shot of how this associated ID could look like:
![](https://board.origin.ogame.gameforge.com/index.php/Attachment/821-apicode-png/?thumbnail=1&s=b7abcd376a6cc008944efda9cfe14efe4eacaa15)
Please keep discussions in this thread technical in nature.
For other feedback please use the separate discussion thread available here: New API for retrieval of combat reports
Raid safely,
DevLaTron
first off, a couple of words about this post: We have been monitoring feedback in the communities about how 3rd party tools interact with OGame. In order to work together on some of these issues we want to try out this new type of "Dev Post". To accommodate all language communities these posts will be made in the Origin Board and in english only. Feel free to direct any potentially interested players / developers to this post.
Now, for the good stuff:
As you have probably heard, with OGame 6.0 changes to the display of Combat Reports (CR) are being made. This has caused concerns about different 3rd party tools breaking because of these changes. To address these concerns and for a more stable solution, we have fleshed out the following:
We wish to offer players the possibility to share combat reports with 3rd party tools in a more simplified and safe manner.
For this we are currently planning a new API that will allow 3rd party developers to directly request combat reports from our servers. In an upcoming snapshot of version 6.0 players will find a new button on their combat reports that allows them to copy a Combat ID to their clipboard (CR_ID).
Using this CR_ID and an application key (API_KEY) issued to 3rd party developers by OGame, tools will be able to directly request the combat information from our server in a machine readable format for storage and processing on their own servers. We *will* be monitoring requests to the API *very* closely.
Please note: The player himself stays in control of which CR_IDs is shared, it will not be possible to retrieve CRs without the ID the player provides.
Our reasonings for this move are the following:
- Combat Report websites will have the opportunity to easily get the information they need without the user having to copy & paste whole combat reports from in game and the site having to parse HTML code.
- Combat reports retrieved this way can not be tampered with by the player issuing the CR_ID to a 3rd party developer.
- The data is easily retrieved and decoded by most programming languages.
- The data is independent of localization, allowing for more cross- community tools.
- Different tools / websites will be able to process the data in different ways, opening up new possibilities for them to present the information they chose to show.
- No more parsing of complex HTML code required.
We are currently still fleshing out the format of the key and the data to be returned by the API, as well as technical formalities that need to be taken care of before we open up this API to the communities.
Additionally, we are working on procedures for requesting API_KEYs from OGame. Most likely, Test Servers will have a global API_KEY for testing purpose, live server can only be accessed with a personalized API_KEY (per tool/website/3rd party developer).
Depending on the acceptance of "API verified" combat reports, we may extend this new API to other pieces of game information in the future, for example alliance or per-user information.
Attached is a mock screen shot of how this associated ID could look like:
Please keep discussions in this thread technical in nature.
For other feedback please use the separate discussion thread available here: New API for retrieval of combat reports
Raid safely,
DevLaTron