Now it’s easier than ever to see the status of our hosted TibiaData API.
Link to our page:
https://status.tibiadata.com
We do use uptime-kuma (github repo) and notifications are sent to our #status-channel on Discord as well.
Kind regards,
Tobias
Now it’s easier than ever to see the status of our hosted TibiaData API.
Link to our page:
https://status.tibiadata.com
We do use uptime-kuma (github repo) and notifications are sent to our #status-channel on Discord as well.
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.2.2 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.2
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.2.1 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.1
Kind regards,
Tobias
We don’t like limiting our service and do consider fair and reasonable as the best way for all of us.
We don’t like users that are trying to walk around our caching in our API gateway, not respect certain error-responses or exorbitant hammering of certain endpoints.
But sometimes things happen that shouldn’t, which then leads to the collective of tibiadata-users to suffering as of the release with v4.2.0.
Due to some heavy use of the highscores endpoint (around 150.000 requests on a 10 minutes period), the creators of Tibia have asked us to implement limitations.
The changed behaviour did create an increase of traffic over 100% and due to the short period of time, it created issues on their side.
Currently the restriction-mode is only enabled on the highscore-endpoints, which were subject to the large change in request behaviour.
You can still use the highscore-endpoint itself, but you the option to use the vocation filtering is removed and you can only use all
as filter.
Not sure about that yet, but hopefully not. We are still in communication with CipSoft about this.
Contact us (preferably on Discord) if you have some low amount of highscore-requests and we can try to figure out a way forward.
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.2.0 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.0
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.1.2 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.1.2
Kind regards,
Tobias
Today it’s finally time for a maintenance of our service due to a migration of our hosting provider.
We are moving after being hosted at DigitalOcean since 2016 to Hetzner Cloud.
For those that are more interested into the technical details, here they are:
If you have issues, please contact us on our Discord server or some alternative mentioned on our Contact us page.
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.1.1 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.1.1
Kind regards,
Tobias
We have released a new version of TibiaData!
You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md
You can find the v4.1.0 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.1.0
Kind regards,
Tobias
As announced the 15th December 2023, the TibiaData API v3 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