Does anyone use the Russian Post SOAP API (advice needed)?

Question

Python

In general, after the recent tricks of the Russian Post in terms of “protecting” the tracking page from parsing, they decided to add verification through official channels in addition to this very parsing. The plan was to use the official SOAPchannels as the main ones and parse as before in case of failure of the main channel. But, apparently, parsing works more reliably.

At first, after receiving the data for accessing the system, on creating a ticket, she stubbornly gave out <error ErrorTypeID="3" ErrorName="Неуспешная авторизация ФК для передачи запроса компоненту получения запросов и выдачи ответов"/>

. After the letter, it turned out to them that even technical support exists there and we were told that the problem was fixed. Now, in the same place, the service returns <error ErrorTypeID="16" ErrorName="Внутренняя ошибка работы сервиса обмена данными"/>

. In general, it seems that they arranged all this in vain and are also trying to put spokes in the wheels of parsing, which works noticeably more stable ...

And so the questions (if you use the SOAP service of the Russian Post, without taking into account the platform):

1. How smoothly did your connection to the service go?
2. How reliable is the service (how often can you see the errors described above)?
3. What are the pitfalls ahead (types of errors, optimal algorithms / running time, etc.)? In general, what can you advise?

Thank you.

Answer 1

Or it can be even simpler - here are the guys doing post2go.ru/b2b/widget You insert
two lines for yourself and you're done. No need to bother with XML parsing and programming in general