REST API: How to deal with processing logic
<p>I read (among others) the following blog about API design: <a href="https://www.thoughtworks.com/insights/blog/rest-api-design-resource-modeling" rel="nofollow noreferrer">https://www.thoughtworks.com/insights/blog/rest-api-design-resource-modeling</a>. It helped me to better understand a lot of aspects, but I have one question remaining: </p>

<p>How do I deal with functionality that processes some data and gives a response directly. Think, verbs like translate, calculate or enrich. Which noun should they have and should they be called by GET, PUT or POST? </p>

<p>P.S. If it should be GET, how to deal with the maximum length of a GET request</p>