An organization has been using agile methodology for software development and testing over 50 sprints of a 2-week cycle each to build a banking application. They are working on automating API testing using REST and documenting the APIs. REST uses HTTP methods like GET, POST, PUT, DELETE along with JSON data and status codes to perform CRUD operations on resources identified by URIs. The documentation describes the URL, HTTP method, request and response formats for different scenarios.

1. Introduction
AGILE METHODOLOGY
.. Development & Testing parallelly in-progress
.. Sprints
2 week sprint
Banking application
50 sprint completed
50 th sprint
.. developer is maknig some change
.. 500 test cases

2. API Automation
• API
ZOMATO 2
orders - 4
chapptis
SWIGGY
10 chappatis
6 chappatis
Food Restaurant
10 Chappati's available

3. • BookMyShow
TicketNew.com
Theatre's own
RAJA Theathre
Some Movie
Specific Show

4. Database
API
Book My Show
TicketNew

5. Exposed
Process APIs
Process
APIs
System API

6. • SOAP
• Heavy weight protocol
• XML
• <main>
• <sub1> data </sub1>
<sub2> data </sub2>
• </main>
• REST
• Light weight protocol
• JSON
• main {
• sub1 : data
• sub2 : data
• }

7. REST
• REpresentational State Transfer

8. • HTTP - Like a vehicle to travel to the destination
• URI - Desitnation
• HTTP Method - Puropse of hitting the server
• CRUD Operation
• POST - to create
• GET - to read
• PUT - to update
• DELETE - to delete
• Request JSON
• {
• “Gender” : “value1”,
• “field2” : “value2”,
• “filed3” : {
• “f3_field1” : “f3_value1”
• }
• }
• HTTP Status code
• 200 - Success
• 201 - Created successfully
• 200 - Put
• 204 - deleted
• 300 -
• 400 - Bad Request
• 403 - Forbidden
• 422 - Data -

9. • API Documentation
• URL / Endpoint
• HTTP Method
• Sample Request Json
• Response code for Positive and Negative scenarios
• Sample Response JSON
• Positive Scenario
• Negative Scenario
• {“error” : “data not av