API version 2 and what’s to come

Hello everyone, here iLxlo_, developer of Filo with a new blog post:

For several months we have been thinking that it was time to update the functions of the Filo API to improve the service we offer. The day has arrived.

We have released the first patches of version 2 of the Filo API and so far it is being a success.

What makes this version different from the previous one?
In this new version of the API we have:
- Strengthening security.
- Improved API responses.
- New endpoints.
- Redesign of Filo’s stats system.
- Privatization of the API.
- Private gateway.

Months ago we have analyzed the traffic that was generated towards our API and we have observed that most could be saved with a few simple clicks, this has been the reason why as of version 2 (including version 2) the Filo API does not It will be accessible to anyone who is previously authorized.
However, despite this privatization, the usual services will continue to function as usual.

As we mentioned before, we have improved the API security, we have implemented some authentication factors in the API and in Cloudflare. We will continue to improve this security as time passes and is necessary.

Another issue that distressed us were the responses and corresponding HTTP codes; it was absolute chaos. We have carefully reviewed each response and assigned an HTTP response code, respecting the standards.

As we have mentioned, we are creating private endpoints that complement the main service, some of them have already been in operation for a few days and we simply do not notify anything about it.

Months ago we changed the sharding system in Filo, this meant that most of our systems in the API were outdated and unusable. Among those affected was Filo’s stat system. After hard work on our part we have managed to create this stats system from scratch and implement improvements and automations in it. Our intervention will never be needed again!

Last but not least, we are going to talk about the Filo API gateway. This is something we’ve been doing for a while. Many of you have suggested that we add more rewards when you vote and when you donate to Filo. We have heard you! The Filo API gateway will allow us to communicate multiple internal services in order to make these suggestions a reality. It’s currently in the internal testing phase and we will not bring it into production until we are 200% sure that it is working properly and there is no security breach in it.

We are aware that we have not mentioned anything related to the Filo status system, we are still investigating tools to be able to reactivate it as soon as possible.

Thanks for reading the article.

Regards.