Tag Archives: JSON

Deploy TibiaData with Helm

Deploying applications on a Kubernetes cluster can be a complex and time-consuming process, requiring manual configurations of deployments, services, and other resources. However, with the advent of Helm the deployment of TibiaData has become significantly easier.

All our charts are available through charts.tibiadata.com.

Add the helm-chart repository
helm repo add tibiadata https://charts.tibiadata.com

Search for charts
helm repo search tibiadata

The charts-repository is located on our GitHub at https://github.com/TibiaData/tibiadata-helm-charts.

Kind regards,
Tobias

TibiaData API v4 beta ongoing

Due to a new error handling, we are bumping our API to a new version since it could interrupt your current integrations.

Our docs have been updated, where you need to select “dev.tibiadata.com” as API server and you can start playing around with the V4 endpoints.

Note

This is the dev environment and endpoints can changed without warning.
This dev environment can be offline unexpectedly.
There is a ratelimit of 2 req/s applied.
The cache for all requests is set to 60 seconds (other timeouts can apply from Cipsoft side).

Contact

Join our Discord server and let’s discuss there or if you experience any issues 🙂

Regards,
Tobias

Maintenance of our service

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

Reminder regarding deprecation of the TibiaData API v2

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.

TibiaData API v2 will be deprecated the 30rd April 2022!

In the update the 1th March 2022, we announced the release of v3. Go check it out here.

Regards,
Tobias

Upcoming deprecation of the 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.

TibiaData API v2 will be deprecated the 30rd April 2022!

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

TibiaData API v3 released (v3.0.0)

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.

Changes of TibiaData API v3

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

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.

The code

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.

Upcoming improvements

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 issues

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.

Thank you!

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

TibiaData API v3 release scheduled

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

Happy New Year

In 2021 there has been happening a lot in the end!
Some of our highlights of the year are:

I’m proud of the progress on the rewrite and new way of how TibiaData is setup and working.
I think there will be a lot happening under 2022 so stay tuned for more stuff to come!

Now go celebrate with your friends and we’ll keep you updated.

And if you got some questions as to the above or so, get in touch with me and I’m happy to answer it all!

Kind regards,
Tobias

TibiaData API v3 beta ongoing

There is a dedicated page for the v3 beta existing, where you can see the current supported endpoints that you can start using.

The page will be replaced with a full normal documentation similar to v2.

Note

This is the dev environment and endpoints can changed without warning.
This dev environment can be offline unexpectedly.
There is a ratelimit of 2 req/s applied.
The cache for all requests is set to 60 seconds (other timeouts can apply from Cipsoft side).

Contact

Join our Discord server and jump into the #v3 channel and let’s discuss there or if you experience any issues 🙂

Regards,
Tobias