EVE Search - Sticky:CREST Killmails Endpoint

Check My IP Information

All Channels

EVE Technology Lab

Sticky:CREST Killmails Endpoint

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]


Author	Thread Statistics \| Show CCP posts - 18 post(s)

CCP FoxFour C C P C C P Alliance 2892	Posted - 2014.02.11 11:29:00 - [1] - Quote Hey guys, You may have noticed in the client when viewing a killmail there was a new option called Copy External Kill Link. Well as of today that link is now live and good to go: When you click on it you should have something like this copied to your clipboard: http://public-crest.eveonline.com/killmails/30290604/787fb3714062f1700560d4a83ce32c67640b1797/ The idea behind this endpoint is that it takes a killmail ID and a hash of the killmail and if the hash is right for that killmail ID we return a response with the contents of the killmail. Assuming killboards build in support for it this means you can API verify a killmail without having to give out your API details. If you run into any problems with this endpoint please let me know here. Enjoy guys! :D CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2893	Posted - 2014.02.11 11:35:00 - [2] - Quote Welp... it does appear I have made a small boo boo with the image links. Will get a fix out soon. CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2898	Posted - 2014.02.11 11:49:00 - [3] - Quote Peter Powers wrote: First of all: i've been asking for this since years, for example on fanfest, so a big and honest: Thank you CCP FoxFour, for making our (3rdparty) world a bit brighter. CCP FoxFour wrote: You may have noticed in the client when viewing a killmail there was a new option called Copy External Kill Link. since i believe not everyone will know what you mean by the new option, here a SC that should help people find it: Screenshot basically its the context menu you can open by clicking at the box to the top left of your killmail. Yes, that one. It's also availible when right clicking on a killmail in a war report or your character sheet. CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2898	Posted - 2014.02.11 11:51:00 - [4] - Quote Sentient Blade wrote: That's cool. Any chance for multiple select in the kill reports window and a way of copying multiple external URLs at once to the clipboard? Newline separated of course. Possibly at some point in the future, but it's really not very high on my list of things to look at. CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2898	Posted - 2014.02.11 11:53:00 - [5] - Quote Captain Thunk wrote: FoxFour is definately the best Furry Dev I... you... just no. No no no. Best dev, great. Furry dev? When have you ever seen me wear anything furry? CCP Nullarbor however... https://twitter.com/CCP_Nullarbor/status/367084848869310464 CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2905	Posted - 2014.02.11 15:31:00 - [6] - Quote I am also aware of an issue where some KMs are returning: application/vnd.ccp.eve.UnsupportedMediaTypeError-v1+json So far I have tracked this to Sleepers, if you are getting this on a killmail without sleepers let me know. :) CCP SocksFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2908	Posted - 2014.02.11 20:51:00 - [7] - Quote Luigi Thirty wrote: Other things: Why doesn't it send faction = null when someone's not in FW like the regular killmail API does? Why does it send every number twice, once in int form and once in str form? Why are corp/alliance icon URLs contained in objects when their only data is the URL? Please don't tell me this is a hacked-together JSON converter on top of MSSQL XML output. In CREST fields can be optional, when something is null we just don't return it. Those fields are optional. I cannot remember the exact technical reasons, but there was some reason for sometimes wanting a string representation. Something about JS not liking long numbers. I actually only put it in once, but CREST takes it and sends both the Long and String version. Um... to be honest I don't know the design reasons for that. It is however the standard for CREST. CCP FoxFour // Game Designer [url]http://twitter.com/regnerba[/url]


CCP FoxFour C C P C C P Alliance 2908	Posted - 2014.02.11 21:27:00 - [8] - Quote Luigi Thirty wrote: CCP FoxFour wrote: In CREST fields can be optional, when something is null we just don't return it. Those fields are optional. If you don't return all fields, is there a list of all possible fields it can return? I don't have access to enough killmails on my personal account to possibly find every field. CCP FoxFour wrote: I cannot remember the exact technical reasons, but there was some reason for sometimes wanting a string representation. Something about JS not liking long numbers. I actually only put it in once, but CREST takes it and sends both the Long and String version. If the problem is numbers that are too big for 32-bit, why not just send them only as strings instead of an integer format that may break applications when it gets too big and let the application worry about manipulating them? The documentation says whats what... but you don't have access to that until CREST is made fully available. Until then you guys will kind of have to put together some docs yourselves. Public CREST is not really a fully supported thing. I will quickly say this: Quote: Killmail: killID - Long killTime - String SolarSystem - Reference - id - Long - name - String moon - Reference - Optional - id - Long - name - String victim - MediaType attackerCount - Long attackers - MediaType KillmailVictim character - Reference - Optional - id - Long - name - String - icon - External Reference corporation - Reference - Optional - id - Long - name - String - icon - External Reference alliance - Reference - Optional - id - Long - name - String - icon - External Reference faction - Reference - Optional - id - Long - name - String - icon - External Reference damageTaken - Long shipType - Reference - id - Long - name - String - icon - External Reference items - MediaType - Optional KillmailItems itemType - Reference - id - Long - name - String - icon - External Reference quantityDropped - Long - Optional quantityDestroyed - Long - Optional singleton - Long flag - Long items - Array - Optional - itemType - Reference -- id - Long -- name - String -- icon - External Reference - quantityDropped - Long - Optional - quantityDestroyed - Long - Optional - singleton - Long - flag - Long KillmailAttackers character - Reference - Optional - id - Long - name - String - icon - External Reference corporation - Reference - Optional - id - Long - name - String - icon - External Reference alliance - Reference - Optional - id - Long - name - String - icon - External Reference faction - Reference - Optional - id - Long - name - String - icon - External Reference securityStatus - Float finalBlow - Bool damageDone - Long shipType - Reference - Optional - id - Long - name - String - icon - External Reference weaponType- Reference - Optional - id - Long - name - String - icon - External Reference CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2908	Posted - 2014.02.11 21:28:00 - [9] - Quote Luigi Thirty wrote: If the problem is numbers that are too big for 32-bit, why not just send them only as strings instead of an integer format that may break applications when it gets too big and let the application worry about manipulating them? This way an application gets to choose and the consumer should be aware of the limitations of their language. Either way it doesn't really matter, it's not something that is up for discussion at this time and I wouldn't be the person to discuss it with. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2912	Posted - 2014.02.12 09:21:00 - [10] - Quote Just to be clear, I don't fully know or understand the decision for both string and none string representation of numbers in CREST. If you would like to talk about the design of CREST come to Fanfest and those that worked on it I am sure would love to talk your ears off. For now though, lets keep this thread focused specifically on this endpoint. There are currently 3 known issues with the endpoint: 1) If a killmail has types on it that were deleted in the past, for example the old probes, the endpoint would choke and die. /sad panda. 2) If there was a sleeper or other NPC on the killmail that belonged to a faction and not a corporation the endpoint would choke. 3) The image links for corporations, alliances, and factions did not work. All three issues have been fixed and should hopefully be deployed during Thursdays downtime. Issue 1 was a tricky fix because there are a few ways to fix it none of which are really that good. The chosen solution is to carry on as normal but replace the name of the item with "Invalid item". Issue 2 was due to some NPCs not being in a corporation. When the killmail is generated in those cases their corporationID is populated with a factionID and the endpoint would choke when trying to match a factionID to a corporation. I now have some special casing in there to deal with this and if a corpID is actually a factionID put it into the faction slot as it should. Issue 3 was really just me not testing well enough. Characters use .jpg and tested fine but corps, alliances, and factions all use .png but I clearly didn't test that and thought they would all be jpg. I was clearly wrong. This has been fixed. Sorry for the brokens but hopefully that should clear up most of the problems. If you have any further issues after Thursday please let me know and I will see about fixing them ASAP. CCP FoxFour // Game Designer @regnerba



CCP FoxFour C C P C C P Alliance 2913	Posted - 2014.02.13 10:39:00 - [11] - Quote Due to me being terrible, occupied with far to many things, and just what not these fixes will not be going out today (Thursday the 13th). I will get them out at the earliest opportunity and will let you know when they go out. So sorry! :( CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2919	Posted - 2014.02.18 14:47:00 - [12] - Quote CCP FoxFour wrote: Just to be clear, I don't fully know or understand the decision for both string and none string representation of numbers in CREST. If you would like to talk about the design of CREST come to Fanfest and those that worked on it I am sure would love to talk your ears off. For now though, lets keep this thread focused specifically on this endpoint. There are currently 3 known issues with the endpoint: 1) If a killmail has types on it that were deleted in the past, for example the old probes, the endpoint would choke and die. /sad panda. 2) If there was a sleeper or other NPC on the killmail that belonged to a faction and not a corporation the endpoint would choke. 3) The image links for corporations, alliances, and factions did not work. All three issues have been fixed and should hopefully be deployed during Thursdays downtime. Issue 1 was a tricky fix because there are a few ways to fix it none of which are really that good. The chosen solution is to carry on as normal but replace the name of the item with "Invalid item". Issue 2 was due to some NPCs not being in a corporation. When the killmail is generated in those cases their corporationID is populated with a factionID and the endpoint would choke when trying to match a factionID to a corporation. I now have some special casing in there to deal with this and if a corpID is actually a factionID put it into the faction slot as it should. Issue 3 was really just me not testing well enough. Characters use .jpg and tested fine but corps, alliances, and factions all use .png but I clearly didn't test that and thought they would all be jpg. I was clearly wrong. This has been fixed. Sorry for the brokens but hopefully that should clear up most of the problems. If you have any further issues after Thursday please let me know and I will see about fixing them ASAP. This fixes have been submitted and should be going out with tomorrows (February 19th) downtime. If you run into any issues after that be sure to let me know. :) Again, sorry for the delay on getting these fixes out. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2921	Posted - 2014.02.19 17:17:00 - [13] - Quote Squizz Caphinator wrote: The fixes were successful. zKillboard currently has over 10k crest endpoints in our database, of which just over 700 of them had errors prior to this release. After the release, only 4 have errors, and 2 of those are invalid hashes. Thanks FoxFour! I will be looking more into these as soon as possible to see if they are just broken killmails or if my endpoint is broken. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2921	Posted - 2014.02.20 14:55:00 - [14] - Quote Hey guys, So with yesterdays release when I attempted to fix the issue with Sleepers and other factions while I did test with factions and making sure that worked I failed to test what happens when there are multiple attackers. The problem basically comes down to me comparing a string to int when checking if someone is in a corporation or not. You can guess how well that went, a whole lot of false negatives. I have a patch ready to go, however it is going to have to wait until Monday. While I know how much this affects you third party guys it's still not really an emergency and deploying anything but emergency patches on a Friday is... well not desired. So Monday will get this fix out and hopefully return things to good. I am also in the process of getting a better test script setup that will use a random selection of killmails from TQ to hopefully find these problems sooner... but even then since the corp field is optional I would have had to see it. TL;DR: I r did dumb dumb and will have a fix out Monday. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2925	Posted - 2014.02.25 20:17:00 - [15] - Quote Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part. I was presented with a potential issue though: https://zkillboard.com/detail/36931325/ The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why. If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2925	Posted - 2014.02.25 20:38:00 - [16] - Quote Steve Ronuken wrote: CCP FoxFour wrote: Just as an update, the most recent hotfix was deployed today and we seem to be good for the most part. I was presented with a potential issue though: https://zkillboard.com/detail/36931325/ The NPC in there, which appears to just be a torpedo, has no corporation listed. I don't know why this would be happening after a quick look over the code but I will continue to dig and see if I can find out why. If you have any other examples of issues or broken things with the CREST killmails endpoint please let me know. It has been a bit of a rough launch and I apologize for that but I am hoping we are through the worst of it now. Thank you for all your patience. Some kills are just bad in game. Like one of the people on my Dread loss has no ship Which makes this all the harder. Killmails are so unreliable right now that I basically have to make everything about them optional and add way more if statements than I ever wanted to. CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2926	Posted - 2014.02.26 09:02:00 - [17] - Quote TheSmokingHertog wrote: wonders about ban hammers and killboard links Not sure what you mean... CCP FoxFour // Game Designer @regnerba


CCP FoxFour C C P C C P Alliance 2932	Posted - 2014.03.03 14:19:00 - [18] - Quote darkchild's corpse wrote: is there an easy way to get the crest api endpoint link from the old api killlog? would be cool to have ONE endpoint to get killmails for posting manually (via crest endpoint) and via old crappy api thingy im not asking you to implement it because its bullshit to work on that old api anymore imo... ( or maybe its just a rly tiny change that takes only 5 mins :3 ) but afaik this is how the endpoint link is build: http://public-crest.eveonline.com/killmails/kill-id/some-magic-hash/ we get the kill ID from the old api.... so thats no problem. but what about the hash? how is that generated? is there an easy way to generate the hash out of the information from the old API? i like the fact that there are item names in the crest api... so i dont have to maintain a stupid item table in my DB \o/ At this point in time we are not ready to say what the hash is, and getting it in the old API is a bit tricky. So no, not at this time. Sorry. :( CCP FoxFour // Game Designer @regnerba

Copyright © 2006-2025, Chribba - OMG Labs. All Rights Reserved. - perf 0,03s, ref 20250716/0737
EVE-Online™ and Eve imagery © CCP.

bitcoin: 1CHRiBBArqpw5Yz7x5KS2RRtN5ubEn5gF

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.