open All Channels
seplocked EVE Technology Lab
blankseplocked Kill Log walking
This thread is older than 90 days and has been locked due to inactivity.

Author Topic

Enraged Stoat
Posted - 2011.06.18 03:24:00 - [1]

I'm trying to walk to character killlog but no matter what beforeKillID value I pass to the 2nd call it returns error 119 kill log exhausted.

First call has no beforeKillID and returns 25 kills.

While processing the kills I determine the highest killID in the results.

That killID is passed into the next API call as the beforeKillID value.

I've tried lowest and highest killID, it always returns error 119 kill log exhausted.

What ID should be used?!

Erik CoolBreeze
Posted - 2011.06.18 05:21:00 - [2]

It probably throws that error because you try to retrieve data before the cache timer has expired.
The cache time for character kills is 60 minutes.

Enraged Stoat
Posted - 2011.06.18 06:45:00 - [3]

Edited by: Enraged Stoat on 18/06/2011 06:45:55
Calling the API repeatedly for the same data within any cache period should generate that yes, but I'm requesting the next page of data, not the same page.

My code gets the first page (by not specifying a beforeKillID), then (if the maximum 25 results were returned) requests the second page specifying beforeKillID. Should be able to walk through the pages within the same cache period. WalletTrans and WalletJournal both work this way, you can make repeated calls using fromID to walk through the data that is beyond the 2560 maximum entries per call. Requesting any page more than once within any cache period should generate the error, but I should not have wait for the timer to expire to request page 2 - that would mean a VERY long wait for all pages.

Thought I was following this wiki on Char_KillLog to the letter "You can scroll back with the beforeKillID parameter listed below."

Is beforeKillID even the correct parameter to pass? If that's wrong the server thinks I'm requesting the same page. Can anyone confirm beforeKillID is what the API server is looking for in the request?

Captain Thunk
Posted - 2011.06.18 08:38:00 - [4]

Edited by: Captain Thunk on 18/06/2011 08:40:05
Character KillLog only returns the last 25 results, you can't walkback.

edit: beforeKillID= is correct, though its for corps

Enraged Stoat
Posted - 2011.06.18 08:56:00 - [5]

Meh, I get it for both char and corp calls :(

Should the value of beforeKillID be the highest killID from the previous results set? Or does it have to be picked by most recent date or something? (i.e. are killID values guaranteed to be higher over time or is the numbering non-linear?)


This thread is older than 90 days and has been locked due to inactivity.


The new forums are live

Please adjust your bookmarks to

These forums are archived and read-only