Feature request: Add all available fleets for a given character to the fleet endpoint

[CodeUrself]

Feature request

Hi!

It came to my attention that the fleet endpoint doesnt list all available fleets for a given character (yet). It would be pretty cool if we could get that endpoint as well, since all other fleet-related endpoints are already implemented.

Route

/characters/{character_id}/fleet/ returns the information about the fleet the character is currently in.

/characters/{character_id}/fleet/all or similar could return all available fleets for the character.

Use case

Fleet participation and other fleet management related things can already be implemented with the existing endpoints, however, fleets are always differently named or run under a different person. Identifying the fleet that needs to be tracked/managed by listening all available fleets first would help this in an automated way.

I think great opportunities for websites that list public NPSI fleets could also emerge. People would be able to see if fleets are being run and who runs it, i'm thinking about Specture Fleet, Zarvox, BjornBee or BombersBar. One quick glance gives everyone the opportunity to find out where they can go to pew pew.
I think it would work great for looser assemblies of more casual groups, newer players or NPSI participants.

Coalition-wide metrics for fleets are currently also heavily favored towards big power blocs, since they have a heavily supporting IT-team that goes above & beyond implementing these metrics manually, by pasting and analyzing D-scans etc. For smaller groups it would be beneficial if that problem could be solved with just an additional ESI endpoint.

Example returns

fleet_id* | integer($int64) returns the fleet ID
fleet_name* | string - Returns the fleet name
fleet_boss | integer($int64) returns the character ID of fleet boss
fleet_location | integer($int64) returns the system ID of the system the fleet is currently in*

This would only apply if the fleet location is set to be displayed, otherwise this would return -1.

Previous XML or CREST route

N/A as far as I know

Thanks in advance!

[CodeUrself]

I'd like to add that it seems the endpoint also already exists on CCP's side but hasnt been exposed to ESI (yet, hopefully).

https://i.imgur.com/GLIDost.png
https://i.imgur.com/5g1xG4T.png

[CodeUrself]

Now, regarding the actual issue, you could probably skip including the fleet_id in the returns as there is no way for you to use that information in the first place without being in the fleet in some fashion.

Agreed. The fleet ID is unnecessary here unless there would be a method to join such fleet with an ESI POST endpoint.

Thanks for the feedback!

[a-tal]

sent for GD feedback

[NyxVxyN]

All I can see is this being automated spying, yet adding to multiple of the nullsec entities bots capabilities...

[Aidansavage]

All I can see is this being automated spying, yet adding to multiple of the nullsec entities bots capabilities...

And how would you explain that? Even beyond the fact that if CCP has reason to believe there's any malicious activity happening with an app, they can disable it? You also say it like people dont already have spies in other entities that can get this information to begin with.

[a-tal]

approved by game design

[a-tal]

the discussion here was all sorts of off-topic. let's try to stay focused on the issue at hand in the future.

apologies, you cannot leave a 👍 reaction on this issue anymore

[jowrjowr]

open for business don't shit it up too hard

[Flupster]

Did this issue ever come to fruition? if not could we get a second look and potentially have this endpoint available, as it stands afaik you still have to guess the fleet boss which can be problematic and bounced failed requests until you figure out the boss