...

Filtering and attribute selection rules are described in the TMF REST Design Guidelines.
Notifications are also described in a subsequent section.

GET API / SLAVIOLATION / {ID}

This Uniform Contract operation is used to retrieve the representation of a managed entity or a task.
Note that collections can be retrieved via GET /api/SLAVIOLATION with no {ID}

...

Example see TMF REST Design Guidelines.

PUT API/ SLAVIOLATION /{ID}

This Uniform Contract operation is used to completely update the representation of a managed entity or a task.

...

Example see TMF REST Design Guidelines.

PATCH API/ SLAVIOLATION /{ID}

This Uniform Contract operation is used to partially update the representation of a managed entity or a task.
Specify which attributes are patchable using the following table (to capture RO attributes)

...

Example see TMF REST Design Guidelines.

POST API/ SLAVIOLATION /{ID}

This Uniform Contract operation is used to create a managed entity or a task.
ID Management :
Specify the ID Management Rule POST without specifying the ID must result in the system generating the ID for the <Entity>. In a specific case, the ID can also be included in the POST (optional)
Attributes required when an entity is created (and their default values if not):

...

Example see TMF REST Design Guidelines.

DELETE API/ SLAVIOLATION /{ID}

This Uniform Contract operation is used to delete a managed entity or a task.

...