This thread outlines the mandatory process for requesting API access for third-party tools interacting with OGame.
Please read this carefully before submitting an application. If you submitted a request before this post, follow the steps and file a new request.
📍 Where to Post
-
All applications must be created in the “Submissions & API Requests” section.
-
The thread must have the label “API Request” selected.
Applications posted elsewhere or without the correct label may be ignored or removed.
🧪 Mandatory Working Demo
A working demo of the tool is required at the time of application.
During development, you may use the following public API readers for testing purposes:
These tools are for development and testing only.
API access for production use must be requested separately via this forum.
Applications without a functional demo will not be processed.
📜 Compliance With 3rd Party Tool Guidelines
Your tool must comply with the official 3rd party tool guidelines, including (but not limited to):
If you are unsure whether a planned feature is allowed, you are expected to contact a ToolDevs responsible in advance and clarify this before implementing or requesting API access.
“We didn’t know” is not a valid justification after submission.
✅ Toleration & API Access
API access will only be granted if all of the following conditions are met:
-
A working demo is provided
-
The tool complies with the 3rd party tool guidelines
-
The tool receives tolerated status
Tools that do not meet these criteria will not receive API access.
Summary
Before submitting an API request, make sure that:
-
You post in Submissions & API Requests
-
You select the API Request label
-
You provide a working demo
-
Your tool follows all 3rd party tool rules
-
You clarified any questionable features in advance
Following this process helps ensure faster reviews and avoids unnecessary delays.
If anything is unclear, please contact a ToolDevs responsible before opening a request.
Thank you for your cooperation.
