Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Resovle Customs Offices location_id #685

Open
GoldenGnu opened this issue Dec 18, 2017 · 2 comments
Open

Feature: Resovle Customs Offices location_id #685

GoldenGnu opened this issue Dec 18, 2017 · 2 comments

Comments

@GoldenGnu
Copy link
Member

@GoldenGnu GoldenGnu commented Dec 18, 2017

Feature request

A way to resolve location_id of Customs Offices (from the character asset endpoint /characters/{character_id}/assets/).

Preferably, using the existing /universe/structures/{structure_id}/ , as that would avoid having to try each location_id in two endpoints (There is no way to identify if the location_id is a citadel or customs office.)

Route

/universe/structures/{structure_id}/

Authentication

Same as is already used

Use case

It's always nice to know where your assets are located.
ATM, there is no way to resolve Customs Offices locations, so, you can only try to guess where the assets are located.

Example returns

Use the existing return from /universe/structures/{structure_id}/

Previous XML or CREST route

None

@warlof
Copy link
Contributor

@warlof warlof commented Jul 30, 2018

Adding some extra location_type like "citadels" or "office" could be usefull aswell 😥

@tillmanj
Copy link

@tillmanj tillmanj commented Jun 11, 2019

There are cases where the only way to find stuff is to brute force check every customs office in every system you have ever had PI in. This would solve that instantly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants