Tag Archives: v2

Minor changes in TibiaData API

There have been a minor change to the TibiaData API regarding the gateway handling the requests.

Earlier, we’ve been using Nginx as handler of the requests, but we have successfully switched to Kong API Gateway instead. This is a first step into upcoming changes..

There are two things we would like to highlight so far.

  1. New headers related to caching by Kong
    API requests are cached in Kong API gateway instead of inside the application and with that there come a few benefits.
    Two new headers that are in place which could be nice for you to know more about:
    • Age – shows the age of the page in seconds (not presented if its not cached)
    • X-Cache-Status – identifies the status of the request’s proxy cache
      • Miss – the request was satisfied by being proxied upstream and parsed fresh data from tibia.com
      • Hit – the request was satisfied and served from cache
      • Bypass – the request could not be satisfied by the cache
  2. Response about page not found/no route existing
    • Earlier behavior, you where presented with a page not found page.
    • New behavior, you will either get a page not found or a JSON response saying there is no route.
    • Future change, you will later on only use JSON responses all the way.

If you want to know more, what the cache intervals are for the different endpoints, you can read our post about TibiaData cache intervals.

Please get in touch with us if you are experiencing any issues and we can try to resolve those.

Regards,
Tobias


Maintenance of our server

Hi there,

Today, we will migrating the API to a new platform and by that, the IP of the API will change.

The support for IPv6 is temporary removed, so the API will now only be available through IPv4.

It should not impact your except if you use the static IP instead of the DNS api.tibiadata.com in your integrations.

Regards,
Tobias


Minor changes in TibiaData API

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

Bug-fixes

  • Characters view
    • HTML changes on tibia.com broke parser (which caused disturbances)
    • first row of tables was ignored but is back again now
    • implementing support for multiple houses (replaced house with houses)
  • Houses view
    • fixing list of all houses

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

Regards,
Tobias


TibiaData API v3 beta delayed

I earlier announced that the v3 beta is supposed to be up and running by now, but there are some issues that need to be addressed first, until you can start testing it.

I’ve received a couple of emails after asking for interest in testing, which is really great! You will get a notification as soon as it’s available 🙂

Best regards,
Tobias


TibiaData API v3 beta

I can announce that TibiaData API version 3 is ready for testing from 24th of July.

There are a lot of changes coming with the newest version and we are very happy to get it out to you soon. Release is scheduled to end of this summer!

The documentation page will soon be updated with new details as well, so stay tuned!

Are you interested in testing our new version of TibiaData? The please drop an email to tobias@tibiadata.com.

UPDATE: some endpoints are not correct yet.. I’m working on them and will post a new update.

Best regards,
Tobias


Minor changes in TibiaData API

There have been a minor change to the TibiaData API regarding the guilds, houses and news views.

Bug-fixes

  • Guilds, Houses and News view
    • images are now served directly from static.tibia.com, instead from TibiaData servers

Credits to Moises Huesca who sent the report of the bug in the API.
Keep the reports coming and feel free to suggest new features too!

Regards,
Tobias


Minor changes in TibiaData API

There have been a minor change to the TibiaData API regarding the worlds views.

Bug-fixes

  • Worlds view
    • worlds with records or ongoing 999+ players have been displayed wrong.

Credits to Jakub Kulpa and who sent the report of the bug in the API.
Keep the reports coming and feel free to suggest new features too!

Regards,
Tobias


Minor changes in TibiaData API

There have been a minor change to the whole TibiaData API regarding CORS (Cross-Origin Resource Sharing).

This means, that you now can run requests with for example ajax towards the API right from your website.

The allowed HTTP methods are GET and OPTIONS.

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to tell browsers to give a web application running at one origin, access to selected resources from a different origin. A web application executes a cross-origin HTTP request when it requests a resource that has a different origin (domain, protocol, or port) from its own.

Source: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

Credits to a lot of you, who have requested this feature in the API.
Keep the reports coming and feel free to suggest even more new features!

Regards,
Tobias


Minor changes in TibiaData API

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

Bug-fixes

  • Houses view
    • beds have need rewritten from spelled to numeric values.

Credits to Lucas Zumpano and who sent the report of the bug in the API.
Keep the reports coming and feel free to suggest new features too!

Regards,
Tobias


Minor changes in TibiaData API

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

Bug-fixes

  • Houses view
    • future prices have been removed and only show the new pricing.

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

Regards,
Tobias