# ESI Market History Endpoint

**URL:** <https://forums.eveonline.com/t/esi-market-history-endpoint/387151>\
**Category:** Third Party Developers\
**Tags:** esi\
**Created:** [December 5, 2022, 5:02pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151 "2022-12-05T17:02:39Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![D43dun](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/d43dun/32/456176_2.png) [@D43dun](https://forums.eveonline.com/u/D43dun)\
**Post date:** [December 21, 2022, 1:04pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/21 "2022-12-21T13:04:35Z")

</div>

Dang DDoSing knucklheads.

After seeing this error when testing the ESI, lead me here. At least there is a good reason.

Any update on progress so far?

---

<div class="post-metadata">

**Author:** ![MAV\_Alleile](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mav_alleile/32/347731_2.png) [@MAV\_Alleile](https://forums.eveonline.com/u/MAV_Alleile)\
**Post date:** [December 23, 2022, 1:06pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/22 "2022-12-23T13:06:59Z")

</div>

Maybe just limit the number of requests to the API from one address per day, for example? Well, or turn on at a certain time. It’s kind of boring without the API.

---

<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:** [December 23, 2022, 2:33pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/23 "2022-12-23T14:33:56Z")

</div>

All ESI bans are IP bans. problems only happens when the attacker are evading the IP ban, as they were in this case and have been in other cases as well. With cloud services like AWS IP rotation is pretty easy. So any limitation by IP will probably be ineffective, as attackers will just rotate the IP. That is why a solution is auth, as you can not rotate eve characters as easy as you can rotate IPs. ESI probably just isn’t hardened enough, because, people used to be super thankful for it and treat it with respect, being good API citizens.

---

<div class="post-metadata">

**Author:** ![Ethan02](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/ethan02/32/378764_2.png) [@Ethan02](https://forums.eveonline.com/u/Ethan02)\
**Post date:** [December 24, 2022, 7:08am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/24 "2022-12-24T07:08:02Z")

</div>

Now also serving static CSV exports that cover the price or order volume (not trade!) history of all items in an entire region on a day or week basis via [https://static.adam4eve.eu/](https://static.adam4eve.eu/). Should help reduce the effort to scrape [the API](https://api.adam4eve.eu/).

---

<div class="post-metadata">

**Author:** ![Attidack](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/attidack/32/308160_2.png) [@Attidack](https://forums.eveonline.com/u/Attidack)\
**Post date:** [December 28, 2022, 4:31am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/25 "2022-12-28T04:31:23Z")

</div>

The best way I’ve found to handle api calls like this would be to put it behind cloudfront which will cache similar requests and return them without touching your API, ec2 instance, lambda, or whatever you have configured.  
It will also cache it at different locations so not only will you have insanely fast cached results, but you’ll also have it geographically closest to the IP making the call so it will be that much faster.

---

<div class="post-metadata">

**Author:** ![D43dun](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/d43dun/32/456176_2.png) [@D43dun](https://forums.eveonline.com/u/D43dun)\
**Post date:** [December 31, 2022, 3:20pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/26 "2022-12-31T15:20:21Z")

</div>

Caching on a CDN is a solution, given that once generated on a daily basis, is static for the rest of the day.

Also, auth would help weed out anyone truly hammering that API. At the very least, make it harder for a to-be DDoSer.

---

<div class="post-metadata">

**Author:** ![Mokaam\_Racor](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mokaam_racor/32/381064_2.png) [@Mokaam\_Racor](https://forums.eveonline.com/u/Mokaam_Racor)\
**Post date:** [January 5, 2023, 12:48pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/27 "2023-01-05T12:48:45Z")

</div>

It is really unfortunate that this end point is down. My own service which many traders use was 100% reliant on this data particularly and there is nothing like it out there, so my site is down until this is (hopefully) up again soon. Ethan’s data is something different though I’m very grateful for what he does.

Also just let this data be a static download, it was already a pain to call every item for every region you required one by one even if you only had to do it once per day.

---

<div class="post-metadata">

**Author:** ![MAV\_Alleile](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mav_alleile/32/347731_2.png) [@MAV\_Alleile](https://forums.eveonline.com/u/MAV_Alleile)\
**Post date:** [January 12, 2023, 9:38am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/29 "2023-01-12T09:38:27Z")

</div>

It can do even nginx.

---

<div class="post-metadata">

**Author:** ![Lars\_Fidard](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/lars_fidard/32/362032_2.png) [@Lars\_Fidard](https://forums.eveonline.com/u/Lars_Fidard)\
**Post date:** [January 23, 2023, 3:51am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/30 "2023-01-23T03:51:22Z")

</div>

This endpoint was taken down after a DDoS on 4 November. 80 days later and it’s still down. I’m sorry to say but that was a hell of a successful DDoS.

And from what I can tell, no news since this topic was created, more than a month ago. **Any** updates on this issue would be appreciated.

---

<div class="post-metadata">

**Author:** ![Geo\_Eclipse\_Oksaras](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/geo_eclipse_oksaras/32/500781_2.png) [@Geo\_Eclipse\_Oksaras](https://forums.eveonline.com/u/Geo_Eclipse_Oksaras)\
**Post date:** [January 23, 2023, 1:25pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/31 "2023-01-23T13:25:09Z")

</div>

> [@ESI - Public Character Data](https://forums.eveonline.com/t/esi-public-character-data/392063/1):
>
> Via @CCP_Swift
> 
> I will add a bit more context as to some of the ESI failures, as it’s, unfortunately, more widespread than this endpoint. he Market data endpoint has been down, and now two relating to character corporation history (though afaik not alliance history), are down or impaired.
> 
> The TL;DR for why these endpoints were taken offline is that there is a third-party developer, or a series of third-party devs, using AWS and requesting information from these endpoints so frequently that it puts the rest of the server at risk. These are on the scale of a 6,000% increase in hourly requests. Typically we’d use IP bans to stop the attack and then players would reach out to us, however, that strategy is no longer working in a climate where AWS can assign another IP immediately.
> 
> The team is aware of how severe these outages are and are actively pursuing solutions that will restore functionality and give us more tools to block errant programs or bad actors without taking the entire service offline.

Just a few days ago, ccp swift went into further detail what happened and why its not a quick fix

---

<div class="post-metadata">

**Author:** ![Laurel\_Celeste](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/laurel_celeste/32/380959_2.png) [@Laurel\_Celeste](https://forums.eveonline.com/u/Laurel_Celeste)\
**Post date:** [February 9, 2023, 11:47pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/33 "2023-02-09T23:47:40Z")

</div>

I think it’s safe to say that the wait for the ESI Market History endpoint has now (2023-02-10) reached a critical stage. Over two months without access to this essential api endpoint is having a huge impact on many tools, developers, and players.

The fact that the endpoint had to be taken down due to the constant spikes in CPU use and the subsequent performance issues is concerning, and it’s clear that immediate action needed to be taken. The market is a crucial component for the game, and the failure of this specific endpoint is having a severe impact on the entire community.

The plans to redesign or add authentication to the endpoint are a step in the right direction, but I think it’s imperative that the work being done is expedited as much as possible. The longer this issue persists, the more damage it will cause to the community and the game as a whole.

I implore the teams involved to find a solution to this situation as soon as possible. The community has been patient for too long, and it’s high time that a resolution is found. I hope that everyone involved is working diligently to restore the market and its endpoint to full functionality.

We can’t afford to wait any longer, and I hope that a solution is found soon. Thank you for the update (although to late and to less) and effort being made to resolve this situation.

GO!

---

<div class="post-metadata">

**Author:** ![Akumi\_Neko\_Gaming](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/akumi_neko_gaming/32/429152_2.png) [@Akumi\_Neko\_Gaming](https://forums.eveonline.com/u/Akumi_Neko_Gaming)\
**Post date:** [February 20, 2023, 11:23pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/34 "2023-02-20T23:23:27Z")

</div>

is there no rate limiter in place?

---

<div class="post-metadata">

**Author:** ![Aiko\_Danuja](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/aiko_danuja/32/481237_2.png) [@Aiko\_Danuja](https://forums.eveonline.com/u/Aiko_Danuja)\
**Post date:** [February 21, 2023, 8:43am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/35 "2023-02-21T08:43:06Z")

</div>

They “temporarily” removed the bounty system in October 2020.

CCP just deleting the game piece by piece.

---

<div class="post-metadata">

**Author:** ![MAV\_Alleile](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mav_alleile/32/347731_2.png) [@MAV\_Alleile](https://forums.eveonline.com/u/MAV_Alleile)\
**Post date:** [February 23, 2023, 9:21am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/36 "2023-02-23T09:21:23Z")

</div>

when?

---

<div class="post-metadata">

**Author:** ![Crash\_888](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/crash_888/32/357008_2.png) [@Crash\_888](https://forums.eveonline.com/u/Crash_888)\
**Post date:** [March 1, 2023, 3:38pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/37 "2023-03-01T15:38:39Z")

</div>

any update?

---

<div class="post-metadata">

**Author:** ![Aiko\_Danuja](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/aiko_danuja/32/481237_2.png) [@Aiko\_Danuja](https://forums.eveonline.com/u/Aiko_Danuja)\
**Post date:** [March 18, 2023, 11:32pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/38 "2023-03-18T23:32:49Z")

</div>

anyone home?

---

<div class="post-metadata">

**Author:** ![Sasha\_Winston](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/sasha_winston/32/505673_2.png) [@Sasha\_Winston](https://forums.eveonline.com/u/Sasha_Winston)\
**Post date:** [March 21, 2023, 7:05pm UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/39 "2023-03-21T19:05:50Z")

</div>

😡 😡 😡

---

<div class="post-metadata">

**Author:** ![MAV\_Alleile](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mav_alleile/32/347731_2.png) [@MAV\_Alleile](https://forums.eveonline.com/u/MAV_Alleile)\
**Post date:** [April 9, 2023, 7:28am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/40 "2023-04-09T07:28:27Z")

</div>

💩 💩 💩

---

<div class="post-metadata">

**Author:** ![AmperXan](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/amperxan/32/348473_2.png) [@AmperXan](https://forums.eveonline.com/u/AmperXan)\
**Post date:** [April 14, 2023, 3:16am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/41 "2023-04-14T03:16:15Z")

</div>

@CCP_Zelus In the short term, has the team considered working with the larger partners and building a static IP whitelist for the API?

---

<div class="post-metadata">

**Author:** ![CCP\_Zelus](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/ccp_zelus/32/382070_2.png) [@CCP\_Zelus](https://forums.eveonline.com/u/CCP_Zelus)\
**Post date:** [April 14, 2023, 11:30am UTC](https://forums.eveonline.com/t/esi-market-history-endpoint/387151/42 "2023-04-14T11:30:06Z")

</div>

It’s a good thought in the event that anything like this happens in the future, we actually considered it as well as a form of mitigation, but the system was designed to be open to all, then closed to specific IPs as required (i.e a blacklist system).

We also don’t want to punish any (new) developers trying to access the endpoints trying to develop apps that are using dynamic IP ranges that need constant updates too.

[Previous page](https://forums.eveonline.com/t/esi-market-history-endpoint/387151.md?page=1)

[Next page](https://forums.eveonline.com/t/esi-market-history-endpoint/387151.md?page=3)
