Skip to content
This repository has been archived by the owner on Jun 4, 2018. It is now read-only.

elDante/eoat

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

57 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

EOAT Build Status Dependency Status

EVE Online API Toolbox a single tool to access the API of a variety resources for the EVE Online.

Support of:

Requirements

  • Ruby 2.0.0
  • httparty

Installation

Add this line to your application's Gemfile:

gem 'eoat'

And then execute:

$ bundle

Or install it yourself as:

$ gem install eoat

Usage

Fast links

EVE API

Use EOAT::EveApi class to retrieve data from the EVE API.

Requests without authorization

Example, get skill tree

require 'eoat'
skill_tree = EOAT::EveApi.new.SkillTree
skill_tree.result # EOAT::Result::EveType::Result class instance
=> ["skillGroups"]
skill_tree.skillGroups # EOAT::Result::EveType::RowSet class instance
skill_tree.skillGroups.columns
=> ["groupName", "groupID"]
skill_tree.skillGroups.key
=> "groupID"
skill_tree.skillGroups.entries # Array class instance
groups = skill_tree.skillGroups.get 1241 # EOAT::Result::EveType::Row class instance or Array
groups.class
=> Array
groups.size
=> 2
group = skill_tree.skillGroups.get 505
group.class
=> EOAT::Result::EveType::Row
group.groupID
=> "505"
group.groupName
=> "Fake Skills"
group = skill_tree.skillGroups.entries.first
group.groupID
=> "1241"
group.groupName
=> "Planet Management"
group.skills # EOAT::Result::EveType::RowSet class instance
group.skills.key
=> "typeID"
group.skills.columns
=> ["typeName", "groupID", "typeID", "published"]
group.skills.get(2403).typeName
=> "Advanced Planetology"
group.skills.entries.each { |skill| puts skill.typeName }
Advanced Planetology
Planetology
Interplanetary Consolidation
Command Center Upgrades

Example, get server status

api = EOAT::EveApi.new(:scope => 'server')
server_status = api.ServerStatus
server_status.result
=> ["serverOpen", "onlinePlayers"]
server_status.serverOpen # String
=> "True"
server_status.onlinePlayers # String
=> "6361"

Example, get character info for characterID=208974814

api = EOAT::EveApi.new
char_info = api.CharacterInfo(characterID: 208974814)
char_info.result
=> ["characterID", "characterName", "race", "bloodline", "corporationID", "corporation", ...]
char_info.characterName # String
=> "Evor Endo"
char_info.corporation # String
=> "NeoCorteX Industry"
char_info.employmentHistory # EOAT::Result::EveType::RowSet class instance
char_info.employmentHistory.entries.last # EOAT::Result::EveType::Row class instance

Example, get factional warfare top stats

fw_stats = EOAT::EveApi.new.FacWarTopStats
fw_stats.result
=> ["characters", "corporations", "factions"]
fw_stats.characters # EOAT::Result::EveType::Row class instance
fw_stats.characters.KillsYesterday # EOAT::Result::EveType::RowSet class instance
fw_stats.characters.KillsYesterday.key
=> "characterID"
fw_stats.characters.KillsYesterday.columns
=> ["characterID", "characterName", "kills"]
fw_stats.characters.KillsYesterday.entries.first # EOAT::Result::EveType::Row class instance
fw_stats.characters.KillsYesterday.entries.first.characterName
=> "trigger99"

Authorized requests

Example, get API key info

key_info = EOAT::EveApi.new(keyID, 'vCode', scope: 'account').APIKeyInfo
key_info.result
=> ["key"]
key_info.key # EOAT::Result::EveType::Row class instance
key_info.key.expires
=> ""
key_info.key.characters # EOAT::Result::EveType::RowSet class instance
key_info.key.characters.key
=> "characterID"
key_info.key.characters.columns
=> ["characterID", "characterName", "corporationID", "corporationName"]
key_info.key.characters.get(208974814).characterName
=> "Evor Endo"

Example, get members tracking

api = EOAT::EveApi.new(keyID, 'vCode', :scope => 'corp')
tracking = api.MemberTracking(extended: true)
tracking.result
=> ["members"]
member = tracking.members.get(208974814)
member.name
=> "Evor Endo"

ZKillboard API

Use EOAT::ZKApi class to retrieve data from the EVE API.

Examples

Get latest solo kill (url)

require 'eoat'
solo = EOAT::ZKApi.new.solo
solo.result
=> ["kills"]
solo.kills.entries.size
=> 200
solo.kills.entries.first.killID
=> "33070118"
solo.kills.entries.first.victim.characterName
=> "Glorfinda Elundario"

or only 10 records (url)

solo = EOAT::ZKApi.new.solo(:limit => 10)
solo.kills.entries.size
=> 10

Get the last 50 kill of a alliance No Value with no items and api verified (url).

result = EOAT::ZKApi.new('no-items', 'api-only').kills(allianceID: 99002003, limit: 50)
result.kills.entries.size
=> 50

Response errors

All specific errors for gem are described in the module EOAT::Exception. Three of these will be described in detail.

HTTP404Error
The error occurs when the response comes back with code 404.
HTTPError
The error occurs when the response comes back with a code other than 200 and 404. To get the error code and response headers, use methods status and headers
EveApiError
The error occurs when EVE API returns the custom XML error. To determine the number of error, use the method number For a complete list of errors can be found here.

Example EOAT::Exception::HTTP404Error

EOAT::EveApi.new.foo
EOAT::Exception::HTTP404Error: Request url path '/eve/foo.xml.aspx' not found

Example EOAT::Exception::HTTPError

begin
  EOAT::EveApi.new(123, 'bar', scope: 'account').APIKeyInfo
rescue EOAT::Exception::HTTPError => e
  puts e.status
  puts e.headers
  puts e.message
end
403
{"content-type"=>["text/html"], "date"=>["Wed, 04 Sep 2013 17:10:05 GMT"], "connection"=>["close"], "content-length"=>["1233"]}
Request host 'https://api.eveonline.com' return error: '403 - Forbidden'

Example EOAT::Exception::EveApiError

begin
  EOAT::EveApi.new(keyID, 'vCode', :scope => 'corp').KillLog
rescue EOAT::Exception::EveApiError => e
  puts e.number
  puts e.message
end
120
Expected beforeKillID [33012983] but supplied [0]. Please supply the expected killID!
If you are not expecting this message it is possible that some other application is using this key!

Caching

To cache the result can be used three types of storage: file, memcached and redis. In the default configuration is used stub cache EOAT::Cache::NoneCache class.

File

The easiest way to cache the result. Since only used space on your hard disk. The default uses the path to store: ~/.eoat/cache.

Set store cache to files in the default path

EOAT.cache = EOAT::Cache::FileCache.new

or set custom path

EOAT.cache = EOAT::Cache::FileCache.new('new/path')

Memcached

Memcached popular key-value database in memory. This is a good choice of places to store the cache. To use it, you must also install an additional dependence gem memcache and of course to have a running memcached.

Set store cache in Memcached using standard connectivity options

EOAT.cache = EOAT::Cache::MemcachedCache.new

or set custom address / port

EOAT.cache = EOAT::Cache::MemcachedCache.new('address:port')

Redis

Redis is a key-value journaling database in memory. Prevents you from losing data after a reboot. To use it, you must also install an additional dependence gem redis and running Redis daemon.

Set store cache in Redis using standard connectivity options

EOAT.cache = EOAT::Cache::RedisCache.new

or set custom address / port or socket

EOAT.cache = EOAT::Cache::RedisCache.new(:host => 'address', :port => port)
EOAT.cache = EOAT::Cache::RedisCache.new(:path => 'path/to/socket')

Additional options

You can set the maximum cache lifetime in seconds. By default, the maximum TTL is set to 30 days. I do not recommend set it in a larger value than the default, if you use Memcached.

EOAT.max_ttl = 259200 # 3 days

Data checking

You can check the relevance of the result. For this purpose there is a boolean parameter from_cache in Result class

Example

require 'eoat'
EOAT.cache = EOAT::Cache::MemcachedCache.new
errors = EOAT::EveApi.new.ErrorList
errors.from_cache
=> false
errors = EOAT::EveApi.new.ErrorList
errors.from_cache
=> true

Additional request parameters

You can also change or add request headers. It may happen that you will be denied to provide data if you do not specify them.

EOAT.headers
=> {"User-Agent"=>"EOAT/0.0.1 (Eve Online Api Toolbox;+https://github.com/elDante/eoat)", "Accept-Encoding"=>"gzip", "Accept-Charset"=>"utf-8"}
EOAT.headers['User-Agent'] = 'Custom User-Agent'
EOAT.headers['From'] = 'user@example.com'

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request