http://eve-kill.net/?a=jsonpilot&pilot=Shellac_Brookdale&year=2011

seems to only return kills in December?

I guess I need a way to limit the last x kills to make it nice to implement into my killboard plugin.

That way I can only pull the number of kills the use wants to display (hard limited to protect your app).

i can then use this and let the user put in pilot name, corp, alliance or eve alliance if they want to use it to show what's going on in a particular location.

(The Amarr System Wordpress blog! ;) )

why not something like:

http://eve-kill.net/GetAlliance/AllianceName.json

or

http://eve-kill.net/Alliance/AllianceName.xml

etc

Much neater imo, and its how I do all my API's

There seems to be a problem with the idfeed since yesterday. It just gives me a "DIIIIIIIEEEEEEEEEEEEEEEEEEEEEEE" text message instead of the XML output. Anything I should be worried about?

o/

Just reinforcing my ideas.

Heres how my API calls are formatted:

• 'v1' = Version (can be stripped out)
• 'public' = API key (can be stripped out)
• 'system' = Service
• 'systeminfo' = Method
• 'solarSystemID' = key
• '30000142' = value to above key
• '.xml' is the format you want the data returned in.

http://api.evejb.com/api/v1/public/system/systeminfo/solarSystemID/30000142.xml

Using this format it turns http://eve-kill.net/?a=jsonpilot&pilot=Shellac_Brookdale&month=11 into:

http://eve-kill.net/api/v1/public/pilot/pilotKills/Shellac_Brookdale/month/11.xml

Which in my opinion looks much nicer, as with long urls makes them easier to read.

You can have unlimited parameters after the 'Method', there's no need to add any more code. (it uses a generic method to get all the parameters)

E.g : http://api.evejb.com/api/v1/public/system/systeminfo/solarSystemID/30000142/someRandomParameter/1234.xml
no code was added to allow that 2nd key/value pair.

Hope this makes sense ?

My API has multiple parsers / returnable formats such as json, xml, txt, cvs , printr, php, any other custom parser you want to create all you need to do is define the class, inherit an interface. May be handy to some people, but more than likely it will be json or xml.

Another nice thing is doing : http://api.evejb.com/api/v1/public/system/help.xml which will get the phpdocs for each method and produce a form of help file containing required parameters etc (although i haven't created any automatic phpdoc for the example)

Sorry, had to kill the idfeed for a bit. It was making the http server unresponsive.
It was actually so bad, that it was doing nothing but answering idfeed requests :/




Would require i started recoding it, haha.. But yeah, it does look much nicer - but im also very very very very very very lazy. :P

Or you could use my code (API Framework) ;)

I made an error:
http://eve-kill.net/api/v1/public/pilot/pilotKills/Shellac_Brookdale/month/11.xml
should be:
http://eve-kill.net/api/v1/public/pilot/pilotKills/pilot/Shellac_Brookdale/month/11.xml

And where would i get said API Framework? :P

also fixed a sorta massive annoying dumb bug in the EPIC API..
I was apparently sorta ******** when i made it, and decided to always include everything, even if nothing was set.
Fixed that, so it only shows what you ask for.. oops :D

Back up now, but I'm struggling to work out how to use this. I'm trying:

http://eve-kill.net/epic/involvedPilot:Dozer Farstrider/mask:2097151

and stealing the mask from one of the examples. Is this like the other API and limited to kills this year? I'm returned back "[]".

I grabbed the name from someone on the front page of eve kill so I know they've got kills!


What I need to do is provide a way for people to put their Pilot name, or Corp name into a box and in the background pull kills from ya to display like this: http://www.innsmouthenterprises.com/wp-content/uploads/2009/07/screenshot-2.gif

and what does that return? Is it limited to kills this year? this month?

Can I get it to return kills in the last x days?

is it possible to make some battle report in some system between two specifics times ?

http://eve-kill.net/?a=kill_related&kll_id=12384045 but between 8:00 to 10:00

I'm trying to set up a new corp KB (edk 4.++), and I'm unable to get data from the current one. How can I retrieve the data from eve-kill?
The most i managed were kills from current month, using idfeed, but since the corp has killmails from 2006 it would be nice to have them all.
Since the biggest problem is my lack of knowledge using idfeed I would appreciate if you can be as specific as you can .
I don't mind doing some legwork, meaning getting mails year by year or month by month even, just need to know if i can get a hold on of all corp killmails.
Regards,
Fara'a

Is there as way to get a copy of the entire set of kills, pilots, corps and alliances directly as opposed to hammering the EPIC API to do so? I.e. MySQL dumps of the corresponding tables gzipped posted somewhere on eve dev periodically would suffice. I can use the API but would rather not be a drain on performance.

There is a bug in the Json produced with your EPIC API if no items are dropped or destroyed (capsule). Instead of creating a null object it creates an empty array. I have left the internal ID so you can reproduce it.

I used the mask value : 1606910

Exemple :

{
"timestamp": "xxxxxxxx",
"internalID": 13002332,
"externalID": xxxxxxxx,
"victimName": "xxxxxxxx",
"victimExternalID": xxxxxxxx,
"victimCorpName": "xxxxxxxx",
"victimAllianceName": "xxxxxxxx",
"victimShipID": xxxxxxxx,
"solarSystemName": "xxxxxxxx",
"involved": [{
"characterID": xxxxxxxx,
"characterName": "xxxxxxxx",
"corporationID": xxxxxxxx,
"corporationName": "xxxxxxxx",
"allianceID": xxxxxxxx,
"allianceName": "xxxxxxxx.",
"factionID": xxxxxxxx,
"factionName": xxxxxxxx,
"securityStatus": xxxxxxxx,
"damageDone": xxxxxxxx,
"finalBlow": xxxxxxxx,
"weaponTypeID": xxxxxxxx,
"shipTypeID": xxxxxxxx
}],
"items": []
}

Can you consider adding the possibility to query the epic api by ids ? e.g allianceId, CorporationId, etc..

Some alliances and corps use a dot at the end and for some reason that character is stripped from the url.

Bump


and