esi
PostUniverseNames endpoint does not support all ID categories
Feature Request
The PostUniverseNames endpoint has two use cases:
- checking the category of an ID
- resolving the name for an ID
It does not support resolving the names of structures and many other categories, which is intended behavior. The problem is that it makes the impossible to learn that an ID is a structure in the first place, so that the dedicated structure endpoint can be called, or another category, so that it can be handled appropriately.
It would be useful to add a structure and other values to the category enum, and either make the name nullable, or have a placeholder value for it in case the ID turns out to be a structure or other category with unresolveable names. Alternatively, a separate endpoint could be created which only returns the category without names.
Use case
Given an ID, I need to know what type of object that is. For example assets endpoints return location IDs that may or may not be a structure (could be a customs office or another category), and it's impossible to resolve the category of these IDs to know what to do with them. Another example are the wallet endpoints which may return context IDs that can be of arbitrary category, like ship item ID for an insurance payout journal entry. It's not possible to tell if an ID is a structure to be resolved with the structures endpoint, or something else.
Checklist
Check all boxes that apply to this issue:
- [x] Feature request description is provided
- [x] Use case exists
- [ ] Feature requires a new route
- [x] Feature adds data to existing route
- [ ] Feature requires new auth scope
- [x] Feature can reuse existing scope
- [x] Feature does not require auth
- [ ] Meta feature, applies to all routes
