# Developer tools

**URL:** <https://forums.eveonline.com/t/developer-tools/22400>\
**Category:** Third Party Developers\
**Created:** [September 6, 2017, 8:44am UTC](https://forums.eveonline.com/t/developer-tools/22400 "2017-09-06T08:44:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shakri\_Manai\_Devolsa](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/shakri_manai_devolsa/32/203341_2.png) [@Shakri\_Manai\_Devolsa](https://forums.eveonline.com/u/Shakri_Manai_Devolsa)\
**Post date:** [September 6, 2017, 8:44am UTC](https://forums.eveonline.com/t/developer-tools/22400/1 "2017-09-06T08:44:40Z")

</div>

Hello,

I am trying to figure out how to get the callback function to work on my application. Any help would be greatly appreciated.

Thanks!

---

<div class="post-metadata">

**Author:** ![Althalus\_Stenory](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/althalus_stenory/32/429792_2.png) [@Althalus\_Stenory](https://forums.eveonline.com/u/Althalus_Stenory)\
**Post date:** [September 6, 2017, 9:12am UTC](https://forums.eveonline.com/t/developer-tools/22400/2 "2017-09-06T09:12:47Z")

</div>

Hello,

I suppose you are speaking about the callback from ESI ?  
If it’s the case:

### if you are in the case of a webapp

You just have to listen to the callback URL in your side, get the code/token (depending on you are in implicit auth or not) and [do what you need with it](http://eveonline-third-party-documentation.readthedocs.io/en/latest/sso/authentication.html#verify-the-authorization-code)

### if you are in a desktop / mobile app

For mobile app, you can use custom protocols and your app can listen to this (iirc we can do this?). For a desktop app, the “easier” (and best way to do this I think) is to start a websocket that’ll listen on “localhost:port” to get your callback url (which you’ll set in [developers.eveonline.com](http://developers.eveonline.com) to be the same).

After, it’s always the same: you get the code/token and you deal with it while notifying the user he’s authed.

Btw, the callback URL in anycase must match the one you set in your application CCP’s side.

_I hope it helps, since your question really lacks informations (language, what you are trying to do, etc etc)_

---

<div class="post-metadata">

**Author:** ![Pete\_Butcher](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/pete_butcher/32/249027_2.png) [@Pete\_Butcher](https://forums.eveonline.com/u/Pete_Butcher)\
**Post date:** [September 6, 2017, 2:42pm UTC](https://forums.eveonline.com/t/developer-tools/22400/3 "2017-09-06T14:42:38Z")

</div>

As for the desktop app - remember that if your local port cannot be opened, you will not be able to authenticate in any way. Period. Some time ago I proposed multiple callback urls, but no feedback yet. Or is there some @Steve_Ronuken ?

---

<div class="post-metadata">

**Author:** ![Golden\_Gnu](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/golden_gnu/32/459734_2.png) [@Golden\_Gnu](https://forums.eveonline.com/u/Golden_Gnu)\
**Post date:** [September 6, 2017, 7:20pm UTC](https://forums.eveonline.com/t/developer-tools/22400/4 "2017-09-06T19:20:04Z")

</div>

For desktop: If you have a site, you can redirect to that as a backup (I simply 64base encode the string and display it on the webpage and allow the user to copy and paste it into jEveAsset), if you can not start your local server. I have two identical apps registrated, one for localhost and one for my site. You can also register with multiple ports in the same way. It does require you keep track of what app ID/secret was used to create each refresh token with, but, that is a do-able.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/eveonline/original/3X/4/1/41ec4921cbaca7a6f9ea556e7cc20018461eae5e.png) [@system](https://forums.eveonline.com/u/system)\
**Post date:** [December 5, 2017, 7:20pm UTC](https://forums.eveonline.com/t/developer-tools/22400/5 "2017-12-05T19:20:06Z")

</div>

Closed on December 5, 2017, 7:20pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
