Skip to main content

REST API (GET,POST,PUT,PATCH,DELETE)

 The word API means application programming interface. Predominantly they are two important protocols which are used in world a) SOAP API (Simple object access protocol) API b) REST API means representational state transfer


API's are used to interact with the web applications, many of the major applications create API's so that the end users can interact with their platform programmatically. Similar to database where we can perform operations such as insert, update, delete. In API's also we can perform such operations. Rest API is one of the highest used API's in the current web applications


So in Rest API we have the following methods calls


a) Get - Get method is used to fetch the data from a web application

b) Post - Post method is used to insert the data into a web application

c) Delete - As the name suggests delete method is used to delete data from a web application, in here we can perform a select deletion or complete deletion as well

d) Put - Put method is used to overwrite an existing record in a web application

e) Patch - Patch method is used to update the record in a application


The difference between put and patch is, In put the record is completely overridden and all its attributes and patch record is used to only update a specific attribute in a record


Comments

  1. The distinction between PATCH and PUT in API design is crucial. PUT replaces a resource entirely, while PATCH updates part of it. Use PUT when a complete update is intended and PATCH for partial modifications, reducing unnecessary data transfer. Choosing the right method ensures efficient and meaningful interactions with APIs, promoting effective data management and optimization. Find more information on PATCH vs PUT.

    ReplyDelete

Post a Comment

Popular posts from this blog

Comparing Objects in Informatica

We might face a scenario where there may be difference between PRODUCTION v/s SIT version of code or any environment or between different folders in same environment. In here we go for comparison of objects we can compare between mappings,sessions,workflows In Designer it would be present under "Mappings" tab we can find "Compare" option. In workflow manger under "Tasks & Workfows" tab we can find "Compare" option for tasks and workflows comparison respectively. However the easiest and probably the best practice would be by doing using Repository Manager.In Repository Manager under "Edit" tab we can find "Compare" option. The advantage of using Repository manager it compares all the objects at one go i.e. workflow,session and mapping. Hence reducing the effort of individually checking the mapping and session separately. Once we select the folder and corresponding workflow we Can click compare for checking out ...

Finding Duplicate records and Deleting Duplicate records in TERADATA

Requirement: Finding duplicates and removing duplicate records by retaining original record in TERADATA Suppose I am working in an office and My boss told me to enter the details of a person who entered in to office. I have below table structure. Create Table DUP_EXAMPLE ( PERSON_NAME VARCHAR2(50), PERSON_AGE INTEGER, ADDRS VARCHAR2(150), PURPOSE VARCHAR2(250), ENTERED_DATE DATE ) If a person enters more than once then I have to insert his details more than once. First time, I inserted below records. INSERT INTO DUP_EXAMPLE VALUES('Krishna reddy','25','BANGALORE','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Anirudh Allika','25','HYDERABAD','GENERAL',TO_DATE('01-JAN-2014','DD-MON-YYYY')) INSERT INTO DUP_EXAMPLE VALUES('Ashok Vunnam','25','CHENNAI','INTERVIEW',TO_DATE('01-JAN-2014',...

Target Load Type - Normal or Bulk in Session Properties

We can see the Target load type ( Normal or Bulk) property in session under Mapping tab and we will go for Bulk to improve the performance of session to load large amount of data. SQL loader utility will be used for Bulk load and it will not create any database logs(redolog and undolog), it directly writes to data file.Transaction can not be rolled back as we don't have database logs.However,Bulk loading is very as compared to Normal loading. In target if you are using Primary Key or Primary Index or any constraints you can't use Bulk mode. We can see this property in the below snap shot.