It is acceptable to create REST api for resources that you don't save to disk, but operate on. The keyword is the "resource" here. You will need to conceptualize it as a resource. For the email example, you can have a POST action for an "email" resource.
It is acceptable to create REST api for resources that you don't save to disk, but operate on. The keyword is the "resource" here. You will need to conceptualize it as a resource. For the email example, you can have a POST action for an "email" resource.
I was thinking the same thing. Thanks