It was already possible to build Tines stories that behave like REST APIs through the webhook API responses menu. One downside of this was the fact that these webhooks could only be reached through webhook URLs, ie https://tenant-name-1234.tines.com/webhook/mypath/mysecret.

Now it's possible to add an API path prefix to response-enabled webhooks. This means the webhook can be reached at https://tenant-name-1234.tines.com/api/public/myapi, so it looks more like a traditional REST API.