A common scenario is to resolve a structure ID into a name. Use the authenticated /universe/structures/{structure_id}/ endpoint for that. It requires a token that grants the esi-universe.read_structures.v1 scope on a character that has docking access to the structure.
The endpoint returns the name of the structure, as well as some additional information such as its system id, type id and the owner corporation id.
There is currently no unified way to discover accessible Upwell structures through ESI. The following methods can be used to discover Upwell structure IDs.
The public /universe/structures/ endpoint will return a flat list of IDs containing all fully public structures. Fully public in this context means a completely open Access Control List. If the ACL prevents even one character from docking the structure won’t show up in this list.
This method has the advantage of not requiring any authentication but is limited in that it only resolves completely public structures. Additionally, most endpoints that consume structure IDs require authentication anyways, so you likely won’t be possible to avoid supplying a token anyways.
The authenticated /corporations/{corporation_id}/structures/ endpoint returns all structures owned by a particular corporation. It requires a token that grants the esi-corporations.read_structures.v1 scope on a character with the Director role in the corporation.
This endpoint provides a lot of information about the structure, including what services are installed and active, when the fuel expires, what state it currently is in etc. Be aware that it currently does not provide the name of the structure.
Some other endpoints may also include structure ids in their results. Structure IDs can usually be distinguished because they are in the int64 range while currently most other IDs are in the int32 range. The following endpoints will often return structure IDs: