Sachin, you raise some interesting points, thanks.
The Recommendation API is not the only API that has no POST - take for example Customer Bill Management (TMF678). That API assumes that bills are created by some automatic process and so can be retrieved (GET) but not created (no POST)
There are of course many ways to generate recommendation, but conceptually we can imagine some offline process crunching the data, creating recommendations, and perhaps sending them proactively to consumers. So the recommendations (like the bills) already exist, just "waiting" to be discovered.
Regarding filters, consult the guidelines document for more details at
https://projects.tmforum.org/wiki/display/PUB/TMF630+API+Design+Guidelines+3.0+R17.5.1 (part 1)
Finally, the lead for this API is Helen (haohongxia) from Huawei, she may be able to provide you with additional information.
Hope it helps.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Mar 01, 2019 16:36
From: Sachin Kale
Subject: Recommendation API TMF680
Hello,
I can see in the specification for Recommendation API, only get api is mentioned as below GET /recommendation?fields=...&{filtering}
The specification does not mention any specific fields to be used for filtering although there are few examples. Just wanted to confirm that it is allowed to freely pass any filters we expect.
Also it does not mention any POST request specifications, so what creates the HREF - "href":"http://serverlocation:port/recommendation/v1/recommendation/1001", in the response?
Thanks for your help
------------------------------
Sachin Kale
------------------------------