Currently, those looking to automate things via Zapier need to save their user/pass with that service for connectivity via XML-RPC. In addition to the obvious concerns, in https://github.com/Automattic/jetpack/issues/14078, a Jetpack user brought up the issue that, when using our crowdsourced brute-force login protection that identifies failed logins by IP across all users of the service, this is resulting in Zapier from being blocked on a lot of various sites.
An WP REST Authentication method that services like Zapier could use to provide oauth or some similar kind of "key" based approach would help prevent this issue.
Currently, those looking to automate things via Zapier need to save their user/pass with that service for connectivity via XML-RPC. In addition to the obvious concerns, in https://github.com/Automattic/jetpack/issues/14078, a Jetpack user brought up the issue that, when using our crowdsourced brute-force login protection that identifies failed logins by IP across all users of the service, this is resulting in Zapier from being blocked on a lot of various sites.
An WP REST Authentication method that services like Zapier could use to provide oauth or some similar kind of "key" based approach would help prevent this issue.