I’m sorry to hear that REST services stopped working reliably. I’d like to revisit this conversation because we will soon remove support for Legacy Rest Services, and I want to make sure the new KPI REST Services interface is working for everyone beforehand. To clarify, we plan to remove:
…in favor of:
We’ll migrate everyone’s Legacy Rest Services automatically to the new interface, where they’ll gain new features like automatic retries, logging, and email notifications to the form owner in case of failure.
@Sarah_Mac, were you using Legacy Rest Services all along, or had you initially used the newer REST Services interface before the problem on August 23? If you identified a problem with the new feature and had to revert to the old system, I want to make sure we fix the issue before discontinuing Legacy Rest Services.
/assets/ URL you’re seeing is used internally by KPI. When you add a REST Service through the new KPI interface (pictured above), this “KPI Hook POST” service is automatically added to KoBoCAT. In a future release, this will be hidden to avoid confusion. No Legacy Rest Service should ever have been changed from any URL you configured to
/assets/…; rather, the
/assets/… URL is always added as an additional service.
The new KPI REST Services feature dates back to late 2018, but your post prompted me to realize that our documentation hasn’t caught up yet. We’ll be publishing a new support article soon.