TibiaData cache intervals

I’ve received a lot of questions regarding realtime data and the cache we use on our side.. so I thought that I will give you some more details!

As from v2 of the API, we’ve implemented a cache, to minimize the resources that we use in for example CPU usage and to lower the amount of requests that poll our service on a seconds bases.
We at TibiaData understand that you want the latest latest data, but when receiving that amount of similar requests, we had to limit it somehow.

The cache we use is a memcached daemon, which stores data in the memory to serve the information faster to you.

Here is a list of the different API requests and the corresponding memcached timeouts.

  • Characters = 300 s
  • Guild/Guilds/Guildwars = 120 s
  • Highscore = 900 s
  • House/Houses = 300 s
  • News/Newslist = 900 s
  • World/Worlds = 60 s

Do you want to contribute with some money to our project? 
Here you can find our PayPal pool for TibiaData:
https://paypal.me/pools/c/7ZbFeDdXZ6

Best regards,
Tobias Lindberg


Maintenance of our server

Hi there,

Our hosting provider DigitalOceans networking team will be upgrading edge networking equipment to improve performance and reliability, where our service is located.

There is a little impact by this maintenance, which may be a few minutes of increased latency as well as small amounts of packet loss while they shift traffic to redundant devices. They will endeavor to keep this to a minimum for the duration of the change.

Start: 2018-11-01 21:00 UTC
End: 2018-11-02 01:00 UTC

Regards,
Tobias


Minor changes in TibiaData API

There have been a minor change to the TibiaData API regarding the characters view.

Bug-fixes

  • Guilds view
    • town of guildhalls missing
  • Houses view
    • the amount of beds was stuck at 1

Credits to Nohus aka Marcin and Henrique who sent the report of the bug in the API.
Keep the reports coming and feel free to suggest new features too!

Regards,
Tobias


Reminder regarding deprecation of the TibiaData API v1

This is just a reminder for you guys, who have missed our last post regarding the upcoming deprecation of TibiaData API v1.

In order to continue to provide great API to you all while implementing new features without breaking things, we need to deprecate the TibiaData API v1.

TibiaData API v1 will be deprecated the 30rd april 2018!

In the post of the 15th december 2017, you can see a full changelog comparing the v1 and v2. Go check it out here.

Regards,
Tobias

 


Maintenance of our server

Hi there,

Our hosting provider DigitalOceans networking team will be performing some proactive upgrades in the datacenter, where our service is located.

Our server should not be impacted by this maintenance, but we still want to mention that there is work going on in the datacenter.

Start: 2018-02-28 21:00 UTC
End: 2018-02-28 23:00 UTC

Regards,
Tobias

 


Upcoming deprecation of the TibiaData API v1

In order to continue to provide great API to you all while implementing new features without breaking things, we need to deprecate the TibiaData API v1.

TibiaData API v1 will be deprecated the 30rd april 2018!

Because the changes and improvements we do can be disruptive, we provide as much advance notice as we can so that you can be ready to make any necessary transition.
So go check out the documentation for the API v2 to see, which those changes are.

In the update the 15th december 2017, you can see a full changelog comparing the v1 and v2. Go check it out here.

Thank you for all the support and love to our API!

Regards,
Tobias

 


Minor changes in TibiaData API

There have been a minor change to the TibiaData API regarding the characters view.

Bug-fixes

  • Highscores view
    • selection of vocation returning wrong vocations due to update on tibia.com

Credits to Ollyx (another supported Tibia fansite called Ollyxpic) who sent the report of the bug in the API.
Keep the reports coming and feel free to suggest new features too!

Regards,
Tobias

 


Maintenance of our server

Hi there,

Our hosting provider DigitalOcean has adjusted their droplets and based on that, we’ve migrated to the new server. This will increase resources to provide an even better service for you!

Our server will be impacted by this maintenance, so during a short period, our API won’t respond.

Start: 2018-01-28 18:00 UTC
End: 2018-01-28 18:03 UTC

Regards,
Tobias