This thread outlines the mandatory process for tools interacting with the OGame API. We have recently streamlined how API access is handled.
1. The Standard Method: Use the Community Proxy
For the vast majority of tools (including all new tools and standalone calculators), you no longer need to apply for a private API key. Instead, you are required to route your API calls through a community proxy.
Please use the following proxy for your tools:
👉 https://ogapi.faw-kes.de/
You do not need permission to use this proxy. Simply build your tool using this endpoint.
2. Requesting a Private API Key (Exceptions Only)
Private API access keys are now strictly reserved for established tool developers who require the absolute reliability of direct API access (e.g., massive user bases, specific technical constraints where a proxy is insufficient).
If you believe your tool qualifies for a direct API key, you must file a request in the “Submissions & API Requests” section with the label “API Request”.
Conditions for requesting a private key:
-
Working Demo: You must provide a working demo of your tool currently functioning via the proxy (
https://ogapi.faw-kes.de/). - Toleration: If your tool interacts with the game (userscripts, addons), it must already have achieved Tolerated status.
- Justification: You must clearly explain why the standard proxy is insufficient for your tool's current traffic or functionality.
Applications without a functional demo or proper justification will be declined.
Summary
- Building a new tool? Use the proxy:
https://ogapi.faw-kes.de/ - Need an exception for direct access? Post in "Submissions & API Requests" with a working demo and justification.
- Clarify any questions with a ToolDev before requesting direct access.
