asset_location_id.md

Asset location_id quick reference

• item_id of the parent asset (Used to build the assets tree, see example below)
• Item ID of the active ship in space If the active ship is in space, the fitting, but, not the ship itself will be returned by the asset endpoint You can get the active ship by combining data from following endpoints:
  • ESI location endpoint
  • ESI ship endpoint
• Asset Safety (location_id == 2004)
• System ID (Range: 30000000 - 32000000)
• Abyssal System ID (Range: 32000000 - 33000000)
• Station ID (Range: 60000000 - 64000000)
• Structure ID Resolvable via:
  • The ESI structure endpoint (if you have docking rights)
  • The ESI bookmark endpoint (all structures you have bookmarked, resolve structures regardless of docking rights)
• Customs Office ID (Those are not resolvable, see ESI feature request, Note: they share ID range with Item IDs and Structure IDs)
• Corporation Office ID (Not resolvable, when location_flag is OfficeFolder, link between Hangars/Divisions (location_flag: CorpSAGx) and Structure/Station ID's.)

Asset Tree example

Flat List

• item_id: 1000000000001, location_id: 60002959
• item_id: 1000000000002, location_id: 60002959
• item_id: 1000000000003, location_id: 1000000000001
• item_id: 1000000000004, location_id: 1000000000003
• item_id: 1000000000005, location_id: 1000000000003

Tree

• item_id: 1000000000001, location_id: 60002959
  • item_id: 1000000000003, location_id: 1000000000001
    • item_id: 1000000000004, location_id: 1000000000003
    • item_id: 1000000000005, location_id: 1000000000003
• item_id: 1000000000002, location_id: 60002959

Fixed Bugs (only relevant for historic data)

• Returned destroyed assets (ESI Issue)
• Returned 9e18 locations (ESI Issue)
• Returned trained skills and active boosters (ESI Issue)
• Returned PI structures (ESI Issue)
• Returned Character IDs (ESI Issue)