Problem description
The two endpoints use POST because they are transferring sensitive data, not because they are creating any resource.
The Commonalities Design Guide states:
When the POST method is used:
- the resource in the path MUST be a verb (e.g. retrieve-location and not location) to differentiate from an actual resource creation
The current paths POST /unconditional-call-forwardings and POST /call-forwardings do not include the verb retrieve to indicate that the are retrieving information only and not creating any resource
Expected behaviour
The endpoint paths need to be renamed by prefixing them with retrieve-. In addition, as POST /unconditional-call-forwardings is retrieving a boolean status value, consider appending -status.
e.g.:
POST /retrieve-unconditional-call-forwardings-status
POST /retrieve-call-forwardings
Alternative solution
None
Additional context
None
Problem description
The two endpoints use POST because they are transferring sensitive data, not because they are creating any resource.
The Commonalities Design Guide states:
The current paths
POST /unconditional-call-forwardingsandPOST /call-forwardingsdo not include the verbretrieveto indicate that the are retrieving information only and not creating any resourceExpected behaviour
The endpoint paths need to be renamed by prefixing them with
retrieve-. In addition, asPOST /unconditional-call-forwardingsis retrieving a boolean status value, consider appending-status.e.g.:
POST /retrieve-unconditional-call-forwardings-statusPOST /retrieve-call-forwardingsAlternative solution
None
Additional context
None