I know the topic seems so interesting right…
APIs are currently one of the hot topics and of course amazing ones too. I am into a relationship with APIs and Postman.
So, I totally enjoyed reading this book too. Currently it’s available in amazon.
My speaking experience in the first international conference….
Conferences are always unique because this will give you an opportunity to meet and greet new people from different places. But this pandemic changed everything. We are drifting towards the virtual world. As you are aware many conferences are made virtual nowadays. In a way that gives you an opportunity to speak in an international conference from the place you are.
I was doing back to back webinars, talks and presentations both internally (inside organization) and externally (through Communities and other Organizations).
I already wrote a blog about women in APIs community…
So far we learnt about the basics of API, how to build an API request, Examples of REST and SOAP API and how to do a JSON schema validation for your responses. Other than schema validation, we have to check some more attributes from the API response. So how do we do that? That’s where we need to create assertions, which are nothing but similar to the front end test cases.
For any application we will be drafting a list of scenarios/test cases to be validated right? …
SOAP is an XML-based protocol for accessing web services over HTTP. It has some specifications which could be used across all applications.
SOAP is known as the Simple Object Access Protocol, but in later times was just shortened to SOAP v1.2. SOAP is a protocol or in other words is a definition of how web services talk to each other or talk to client applications that invoke them. The diagram below shows the various building blocks of a SOAP Message.
Details and methods on parsing the REST response in Postman
REST (Representational State Transfer) is an architectural style for providing standards between computer systems on the web, making it easier for systems to communicate with each other. REST-compliant systems, often called RESTful systems, are characterized by how they are stateless and separate the concerns of client and server. Most commonly used nowadays.
Separation of Client and Server
In the REST architectural style, the implementation of the client and the implementation of the server can be done independently without each knowing about the other. This means that the code on the…
When you start working with third-party APIs, you would have noticed different API authentication methods. This will provide you the authorization for accessing those APIs.