Hi Paras
This is a great question. It is true that for retrieval of managed entities you would generally do a GET. But ServiceQualification is not a managed entity - it represents a non-CRUD business operation. For such operations we use Task resources, as described in the design guidelines TMF630. POSTing a task resource is equivalent of calling e.g. a SOAP or EJB operation.
I suggest you consider what a GET might look like for service qualification (or address validation, or similar), and hopefully you will come to the conclusion that GET is not relevant for these cases.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 17, 2022 11:37
From: Paras Agrawal
Subject: TMF645 - ServiceQualification POST vs GET
Hi,
I need to expose an API layer to be used by Servcos to check fiber service technical feasibility in a Netco based on location.
The TMF645 mentions using ServiceQualification API POST method for this. Can anyone please help why instead of GET we are using POST here?
Regards,
Paras
#OpenDigitalArchitecture
------------------------------
Paras Agrawal
Infosys
------------------------------