The Plati account without manual sign-in: session and auto-login
SelyaThe balance, claims and advertising payments exist only in the Digiseller account, which stands on a session that drops. Below is how to set up auto-login.
A bot runs Plati listings, prices, orders and chats through the Digiseller API, and for them the Seller ID and the key are enough. But some data lies only in the my.digiseller.com account, which opens by a session, as in a browser.
What is only in the account
- The balance with unfreeze dates, and withdrawals.
- Buyers' claims. They must be answered in time, and the API does not give them.
- Advertising payments.
What the API itself can and cannot do is covered in the article “Plati and the Digiseller API”.
Why the session “drops”
The account session is a cookie, and it lives for a short time. If a bot does not visit the account, it expires after a while and the data stops updating. So the session has to be kept alive: open an account page regularly, and sign in again when it has died anyway.
A trap that is easy to fall into: a network failure, a 429 answer, a 5xx error or a 403 from Digiseller does not yet mean the session has died. If you sign in again after every such answer, you can waste captchas for nothing and run into sign-in limits.
Auto-login step by step
- In the my.digiseller.com account open the personal account, then Security and the WM authorization tab. Choose “required only for working with the content and description of products…” or “not required”. Why is below.
- Open an account at rucaptcha.com, take the API key in the profile and top up the balance with $2–3.
- Give the bot the login and password of my.digiseller.com and the RuCaptcha key. A sign-in with a captcha takes 1–2 minutes.
- Check that the session is active and see what the bot reported about the successful sign-in.
If you do not want to give the password, sign in to the account in your own browser and give the bot the session cookie. While the bot visits regularly, the session is extended. But once it does expire, the cookie has to be pasted again.
WM authorization gets in the way of auto-login
If the account has “WM authorization: always required at sign-in” on, signing in goes not through the Digiseller form but through WebMoney Login: a phone or WMID, a password, a picture and sometimes a confirmation code. A server cannot pass such a sign-in.
The middle option (“only for working with the content…”) keeps the WebMoney confirmation for sensitive sections, while Sales and Claims open with the login and password. For safety you can turn on IP blocking and add your server's IP. If you turn on blocking and forget about the server, auto-login stops working.
What RuCaptcha costs
A captcha is solved only at sign-in, not at every session check. In our experience it comes to about 5 cents a day, roughly $1.50 a month. If you sign in no more than once in 30 minutes, that is at most 48 sign-ins a day per account. The exact price of a solution is in the rucaptcha.com account.
What the errors mean
| Message | What to do |
|---|---|
| Session expired | Auto-login is not set up or could not sign in. Set it up or paste fresh cookies from the browser. |
| Wrong login or password | Check them and try signing in to my.digiseller.com by hand. |
| Signed in, but the session was not accepted | Most often IP blocking is on without the server's IP, or WM authorization is set to “always”. |
| Sign-in was redirected to WebMoney Login | Switch WM authorization to the middle option, as described above. |
| RuCaptcha balance exhausted | Top up the balance and signing in continues by itself. |
| Captcha solving error | The next attempt is usually enough. If it will not solve at all, check the RuCaptcha key. |
| The account does not answer several checks in a row | A failure on Digiseller's side or in the network, it passes by itself. Nothing to change. |