DOCSEARCHbyAlgolia
Submit Docs

ESI (EVE Swagger Interface) Issue Tracker

repository·master·Indexed 42 days ago

https://github.com/esi/esi-issues

The official issue tracker for EVE Online's ESI API and SDE (Static Data Export). Provides templates and guidelines for reporting bugs and requesting features for the API and data files on the Tranquility server.

Tokens
801
Snippets
4
Records
6
Agent score
3%

What's inside ESI

  1. Important guidelines for opening issues

    master

    Before opening an issue in this repository, adhere to the following constraints:

    • Scope: Only submit issues related to ESI. For in-game issues, use the in-game functionality.
    • Server: Only submit issues for the Tranquility server. For other servers, use in-game functionality or customer support.
    • Security: Do not open security-related issues here. Send an email to security@ccpgames.com instead.
    • Search First: Always use the GitHub search function (including closed issues) before opening a new issue.

  2. Report a bug in ESI (API)

    master

    Use the ESI bug report template to report issues related to the EVE Online API (ESI).

    Valid bug examples:

    • Unexpected 500 responses.
    • Incorrect information in the API specification.
    • Invalid or unexpected response formats.

    Note: Errors such as 429, 502, 503, or 504 are not considered bugs; please retry your request at a later time.

    https://github.com/esi/esi-issues/issues/new?template=bug_esi.yaml

  3. Request a new feature in the SDE (Static Data Export)

    master

    Use the SDE feature request template to suggest additions to the Static Data Export. Note that some new data may require game design approval.

    Valid feature request examples:

    • Adding a field to an existing data file.
    • Exposing a new data file.
    https://github.com/esi/esi-issues/issues/new?template=feature_request_sde.yaml

  4. Request a new feature in ESI (API)

    master

    Use the ESI feature request template to suggest improvements to the API. Note that some requests may require game design approval.

    Valid feature request examples:

    • Adding an attribute to an existing route.
    • Exposing other available client data.
    • Meta requests, such as adding global parameters to the specs (e.g., ETag, Accept-Encoding).

    Best Practices:

    • Search for existing requests before opening a new one to avoid duplicates.
    • If a similar request exists, use the 'thumbs up' reaction on the parent comment.
    • If you have a different use-case for an existing request, add it as a comment.
    https://github.com/esi/esi-issues/issues/new?template=feature_request_esi.yaml

  5. Report a bug in the SDE (Static Data Export)

    master

    Use the SDE bug report template to report issues with the Static Data Export files.

    Valid bug examples:

    • A value that does not match what the game client shows.
    • Missing or duplicated entries in a data file.
    • A file that fails to parse, or a field with an unexpected type.
    https://github.com/esi/esi-issues/issues/new?template=bug_sde.yaml

  6. ESI Resources and Documentation

    master

    For developing with EVE Online's API, use the following resources:

    • Direct API: https://esi.evetech.net/
    • API Explorer: https://developers.eveonline.com/api-explorer (Lists all changes related to ESI routes).
    • Changelog via API: Available via the GetMetaChangelog route in the API Explorer.
    • Official Documentation: https://developers.eveonline.com/ (Includes blog posts, best practices, guides, and formulas).
    • Community Support: Discord #3rd-party-dev-and-esi channel.