We have still seen a lot of requests coming in to the deprecated V2 API endpoints, which is the reason why we’ve had a grace period before terminating those requests.
But since V2 is deprecated and should have switched over the V3 by now, we’ve disabled all V2 endpoints by today 14:55 CEST.
A server restart will also take place around that time, which should only interrupt the service for around 1-2 minutes.
Kind regards,
Tobias
As announced the 15th March 2022, the TibiaData API v2 has now been deprecated.
This means that you can not use our API anymore, if you do requests towards the old URLs.
Go ahead and upgrade your application, to be able to continue to use our API.
Regards,
Tobias
Hello there,
Our hosting provider DigitalOcean will make changes in the networking equipment to improve performance and support future functionality of our hosting location.
This maintenance is expected to not have any impact on our services, except for a risk of increased latency as well as small amounts of packet loss while the upgrades are performed.
Maintenance window:
Start: 2022-05-03 16:00 UTC
End: 2022-05-03 19:00 UTC
Regards,
Tobias
This is just a reminder for you guys, who have missed our last post regarding the upcoming deprecation of TibiaData API v2.
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 v2.
In the update the 1th March 2022, we announced the release of v3. Go check it out here.
Regards,
Tobias
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 v2.
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 v3 to see, which those changes are.
In the update the 1th March 2022, we announced the release of v3. Go check it out here.
Thank you for all the support and love to our API!
Regards,
Tobias
A long waiting is over now.. today it’s finally time some new stuff!
Today we can announce that version 3 of TibiaData API is released!
Through our API, you can have access to an API providing information of characters, guilds, highscores, worlds and a lot more of Tibia.
You can based on the request provided by us build your own clients to retrieve the information you need.
Since v3 is a rewrite of TibiaData from PHP to Golang, the difference between v2 and v3 is larger than between v1 and v2.
Therefore we’ll not have a changelog list as we did in last release.
There have also been additions of endpoints like creatures, fansites, killstatistics and more.
Head over to our documentation to play around with our API and get your tools migrated to v3.
The documentation from v3 has been swagger-generated, so you can easily generate your own TibiaData client to consume our API.
You can find the swagger.json file in our tibiadata-api-docs repository on GitHub.
There is a swagger-documentation page available on https://docs.tibiadata.com, where you can play around.
As mentioned in previous blog posts, TibiaData is now publishing it’s code publicly on GitHub.
Dig around and contribute to our repo to enhance our service.
You can find all our repos under our GitHub organization here.
We’ve also bumped the GitHub release version to match the API version.
We don’t have any proper error handling yet in addition to some other few minor things.
Therefore there will be some addition in the couple of days, but those will not impact you going from v2 to v3.
There will be separate blog posts when those are being added.
Report to us, if you find something that is not correct.
Suggest to us, if you are missing some feature and we’ll implement it.
Special thanks to Kennedy (aka kamilon) and Pedro for the huge amount of contributions to TibiaData and thanks for everyone testing and reporting issues.
Try it yourself!
Kind regards,
Tobias
Testing of v3 is ongoing and we are in the final stage.
Our v3 is planned to be release the 2022-03-01!
The plan is to have v2 and v3 running in parallel for a period of 2 months and v2 is supposed to be deprecated the 2022-05-01.
Head over to our documentation page on docs.tibiadata.com and start on getting your integrations working for the new version.
Join our Discord server and jump into the #v3 channel and let’s discuss there or if you experience any issues 🙂
Kind regards,
Tobias
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.
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
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
There have been a minor change to the TibiaData API regarding the characters views.
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
Join TibiaData on Discord now.
TibiaData is present on GitHub.
Join us and contribute!
Look in our FAQ for some commonly asked question like rate limiting or caching.