Mail updates have 2 reasons to exist: - massive, bulk updates that would otherwise take too long to execute; - fire & forget, just send in the update and it would get processed eventually no matter what.

In the age of REST APIs, neither of the above stands anymore. Currently mailupdates is kept as a fallback and/or legacy interface.

IIRC, there is an update limit for the current REST API (something like 2000 updates per day)

I think what you really want is being able to authenticate via REST API, so that you would be able to query and update your own objects without any kind of dummification or accounting process. Maybe even be able to use an APIKEY over https for a simple way of authentication?

the REST API uses the maintainer password via HTTPS. see also https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API for further details. there are also some client libraries for the REST API out there. Best regards, Alex -- velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588 Tel: +49 6181 1898119 * http://www.velia.net Follow us on twitter: https://twitter.com/velia_net