EF-Map API Access

This page is for trusted third-party builders working on EVE Frontier tools, dashboards, overlays, bots, and research projects. If you reached it because a request to an ef-map.com/api/* endpoint returned a no_origin message, you are in the right place — it explains what API access is, why some endpoints are protected, and how to request a partner key.

What this page is

EF-Map serves most of its experience directly in your browser, but it also exposes a set of heavier shared-data endpoints under https://ef-map.com/api/*. To keep those endpoints fast and affordable for everyone, they are protected.

• Normal EF-Map use is automatic. When you use the map at ef-map.com, the site's own requests are recognized as same-origin browser traffic and just work — no key, no setup.
• Third-party tools and scripts may need a key. A standalone tool, bot, spreadsheet, or backend service that calls these endpoints from outside the site does not look like a browser on ef-map.com, so it needs an EF-Map API key.

Why API access is controlled

The protection is not about locking the community out. It exists so EF-Map stays healthy:

• Prevent abuse and scraping that would otherwise hammer the shared endpoints.
• Keep hosting costs predictable. These endpoints are backed by Cloudflare Workers and KV/edge storage, and uncontrolled traffic translates directly into cost.
• Keep EF-Map reliable for players who are using the live map.
• Let trusted builders integrate responsibly through a stable, supported surface instead of fragile scraping.

What access can cover

Access is granted per scope. A scope is a named group of related read-only endpoints, so a key only carries the data categories a project actually needs. Each scope below links to a live example request and response so you can see the data shape before requesting access. The current scope groups are:

Requesting access

Access is granted case by case. When you reach out, it helps to include:

• Who you are / project name — you and the tool you are building.
• What you are building — a short description of the tool and its audience.
• Which endpoints / data you need — the scopes above that fit (it is fine to ask for guidance).
• Expected traffic — rough request volume and how often you will call.
• Public or private — whether the tool is public, private, or internal to a tribe/group.
• Contact method — how to reach you for key delivery and any follow-up.
• Attribution — public tools credit and link EF-Map (see the terms of use).

Contact

Email [email protected] with the details above to request a key. For abuse reports or a compromised key, use [email protected].

There is no automated self-service signup. Keys are issued manually to keep the partner surface trustworthy, so allow a little time for a reply.

Using a key

Once you have a key, send it on every request in the X-API-Key header. Same-origin browser traffic from ef-map.com does not need this; external callers do.

# curl
curl -H "X-API-Key: YOUR_API_KEY" https://ef-map.com/api/killboard-snapshot

// JavaScript fetch
fetch('https://ef-map.com/api/killboard-snapshot', {
  headers: { 'X-API-Key': 'YOUR_API_KEY' }
})

Replace YOUR_API_KEY with the key you were issued. Your key only unlocks the scopes granted to it; a request for an endpoint outside those scopes returns an insufficient_scope error.

Responsible use

• Cache responses where you can. This data does not change second-to-second, so cache it and reuse it.
• Avoid aggressive polling. Poll on sensible intervals rather than in a tight loop. A generous per-IP rate limit protects the service as a safety net, and well-behaved tools never get close to it.
• Do not redistribute or embed your key in public client-side code, shared repos, or other people's tools. Treat it like a password.
• Ask before building a high-volume integration. If you expect heavy or unusual traffic, mention it up front so we can plan for it.
• Keys can be rotated or revoked. If a key is leaked, abused, or simply needs refreshing, it can be rotated or revoked at any time. Let us know if yours is exposed and we will issue a new one.

Terms of use

Using an EF-Map API key means agreeing to these terms. They cover every scope and every key, including keys issued before they were published on 20 October 2026. The terms on key sharing and request logging were added on 21 October 2026.

• Credit EF-Map. A public tool that shows data from the partner API credits EF-Map with a visible link to ef-map.com near where that data appears.
• Do not re-serve the data. Cache responses for your own tool, but do not republish them as your own API, feed, download or dataset for other tools to consume.
• Respect Fog of War. Community map data exists because players chart the universe under the developers' Fog of War design. Do not combine it with client-extracted or datamined data to reveal systems, positions or contents players have not charted, and do not use it in a tool that shows the whole universe map.
• Use the key for the tool you described. A key is issued for the project in your request. Ask before using it for something materially different.
• Keep your key to yourself. A key belongs to the person and project it was issued to. Do not share it or pass it on, and do not use someone else's key.
• Requests are logged. Each request made with a key is recorded with its time, method, host, route and result, the caller's IP address, what Cloudflare reports about that IP (approximate country, region, city, coordinates and time zone, the network's number and name, and the data centre that answered), the user agent, the request's origin, and the calling Cloudflare Worker's zone if there is one, so that abuse and shared keys can be spotted. These records are kept for 90 days, then deleted, and are left out of database backups.
• Do not sell the data. Do not resell access to it or put it behind a paywall without agreement.
• Access can change. Scopes, response fields and rate limits can change, and access can be limited, suspended or ended at any time, with or without notice, including when these terms are not followed. Keys are reviewed when a new cycle starts.
• No warranty. Data is provided as is. It can be delayed, incomplete or wrong, and availability is not guaranteed.

Not everything is available

The partner API is a curated, read-only surface — not a full backdoor to EF-Map internals. Some things are intentionally out of scope:

• Some endpoints are same-origin only and are not offered to third parties at all.
• Some surfaces are wallet-, subscription-, or allowlist-scoped (for example identity-aware or partner-specific app routes) and are not part of the general partner key.
• Admin and operational endpoints are not exposed.
• Raw backend service hostnames are not a supported integration target. Integrate only through https://ef-map.com/api/*; the underlying data services are an internal boundary and may change.
• Access is read-only unless something else is explicitly agreed.

EVE Frontier is a Fenris Creations / community universe; EF-Map is an independent community tool. Indexed data can be delayed, incomplete, or inference-heavy — treat it as evidence, not absolute live truth. For general questions see the FAQ and About pages.