Use a DELETE API to delete resources that are identified by the Request-URI.
A successful response to DELETE requests SHOULD be:
DELETE operations are idependent. When a resouce is deleted, it is removed from the collection of resources and remains so, even when the DELETE API is called on the same resource repeatedly. The 404 NOT FOUND response code is returned when the DELETE API is called on a deleted resource for the second time. Some may argue that this makes the DELETE method non-idempotent. It is a matter of discussion and personal opinion.
If the request passes through a cache and the Request-URI identifies one or more currently cached entities, these entries SHOULD be handled as stale. Responses to this method are not cacheable.
http://<Domain name>:<PORT>/api/[VERSION_NO]/<LU Name>/<iid>&token=<TOKEN NAME>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/lu/PATIENT/1?token=ABC
Delete LUI 1 from PATIENT LU
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
http://<Domain name>:<PORT>/api/[VERSION_NO]/lu/<LU Name>/<iid>/<TABLE_NAME>&token=<API Key>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/lu/PATIENT/1/INVOICE?WHERE=CUSTOMER=1 or NAME=’LION’&token=ABC
Delete data from PATIENT LU instance id 1, INVOICE table by where clause
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
http://<Domain Name>:<PORT>/api/[VERSION_NO]/COMMON/<COMMON TABLE NAME>?<WHERE CLAUSE>&token=<API Key>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/COMMON?CITIES&WHERE CITY_ID=1&token=ABC
Delete data from CITIES common table where city_id = 1
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
Delete works like GET. All parameters should be populated on the URL or header.
Use a DELETE API to delete resources that are identified by the Request-URI.
A successful response to DELETE requests SHOULD be:
DELETE operations are idependent. When a resouce is deleted, it is removed from the collection of resources and remains so, even when the DELETE API is called on the same resource repeatedly. The 404 NOT FOUND response code is returned when the DELETE API is called on a deleted resource for the second time. Some may argue that this makes the DELETE method non-idempotent. It is a matter of discussion and personal opinion.
If the request passes through a cache and the Request-URI identifies one or more currently cached entities, these entries SHOULD be handled as stale. Responses to this method are not cacheable.
http://<Domain name>:<PORT>/api/[VERSION_NO]/<LU Name>/<iid>&token=<TOKEN NAME>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/lu/PATIENT/1?token=ABC
Delete LUI 1 from PATIENT LU
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
http://<Domain name>:<PORT>/api/[VERSION_NO]/lu/<LU Name>/<iid>/<TABLE_NAME>&token=<API Key>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/lu/PATIENT/1/INVOICE?WHERE=CUSTOMER=1 or NAME=’LION’&token=ABC
Delete data from PATIENT LU instance id 1, INVOICE table by where clause
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
http://<Domain Name>:<PORT>/api/[VERSION_NO]/COMMON/<COMMON TABLE NAME>?<WHERE CLAUSE>&token=<API Key>&[format=json/xml]
Example:
http://localhost:3213/api/v1.0/COMMON?CITIES&WHERE CITY_ID=1&token=ABC
Delete data from CITIES common table where city_id = 1
Request Body: null
Response Body: null
Response code: 200 if delete ended successfully
Delete works like GET. All parameters should be populated on the URL or header.