Being on time is crucial for any business worldwide. When it comes to retrieving data, it’s even more important as automatic tools are supposed to be fast and meet strict digital deadlines.

We’ve already rolled out a video guide about our callbacks adjusting and we hope you successfully use our postback_url solution. Obviously, you should be kept abreast regardless of whether the task is completed and use data right after it’s availability.

Sure enough, the instant data availability isn’t the only thing we should work on and care about. Your particular convenience and experience is equally important for us. That’s why we did some improvements to our postback_url feature.

Postback_url data is fully UTF-8 encoded now 🔲
So, earlier you could receive some values and Unicode string encoded. However, nobody bet all the data should be organized properly and encoded accordingly. That’s why now we decided to simplify your work and decrease your servers’ loading by boiling down everything to UTF-8 encoding.

After the release, which we plan to roll out on 29th of July, all the data you receive within a postback will be UTF-8 encoded.

If your system automatically decoded some Unicode symbols, there is nothing to worry about and you don’t need to apply any changes in that case.
This improvement will affect your system only from the one simple side - no need to decode and change the API output - it will be definitely received with the mentioned encoding.

Found something confusing or have any questions?
Contact our pleasant Support Team!