Tag: API

Creating Json Object From string in Java (Rest-assured):

https://mvnrepository.co m/artifact/org.json/json/2 0210307

get org.json from maven

add below dependency to your maven:

<!--
https://mvnrepository.com/artifact/org.json/js
on -->
<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20210307</version>
</dependency>

Now import these:

//import these 
import org.json.JSONException; 
import org.json.JSONObject; 
import org.json.JSONArray;

Now you can convert a json string to json object just like that:

//now you can convert string to array and
object without having complicated maps
and objects
try {
JSONArray jsonArray = new
JSONArray("[1,2,3,4,5]");
//you can give entire jsonObject here
JSONObject jsonObject = new
JSONObject("{\"name\": [\"praveen\"]}");
System.out.println("outputarray: " +
jsonArray.toString(2));
System.out.println("outputObject: " +
jsonObject.toString(2));
} catch (JSONException err) {
System.out.println("Error: " +
err.toString());
}

Sending request as

Response response = RestAssured.given() .header("Content-type", "application/json") .and() .body("{\r\n" + " \"name\": \"praveen\",\r\n" + " \"job\": \"leader\"\r\n" + "}") .when() .post("https://reqres.in/api/users") .then() .extract().response(); System.out.println(response.prettyPrint());

The hidden gem: Postman API and Documentation feature

its easier than you would expect to create a project collection…

Postman API Feature:

you can create collection , mock servers, documentation in click of a button by using postman API definition feature.

Lets see how to do it!!

  1. Get the API definition:

postman supports following API definitions:

so what is API definitions ?

API definitions, or API specifications or description formats (all are the same) defines your API . It is like a live documentation on what is available, what it can do , what is supported etc . In short a comprehensive live documentation that can help consumers understand what your API can do.

in summary:

  • Help internal folks understand the API and agree on its attributes
  • Help external folks understand the API and what it can do
  • Act as live documentation on what all endpoints are available, what methods are supported, what attributes are expected etc.

https://swagger.io/blog/api-development/why-you-should-create-an-api-definition/

How to get API definition ?

Most APIs visualizes the API definition using swagger UI. Which creates a user interactable representation of your API from the API definition file.

In mostcases the swagger UI will have link to the definition file or you can goto network tab and search for it

lets take https://petstore.swagger.io/ as example.

you can see the link to the definition file, it can be in yaml or json format. just click the link and copy the content.

you can see the version is swagger 2.0 meaning its open api v2

2. Create API in Postman

click API section and click the add icon or create new API link

Now give the below details:

name,version , open api v2.0 and json , and click create

Now paste the swagger definition we copied from pet store:

you can press ctrl+b to format the json properly after pasting:

click save

3. Now Generate collection from this swagger definition:

click generate collection:

click show advanced settings:

Give the below settings:

Now click Generate collection and goto your collections once the collection generation completes

4. Mock server , documentation and other things

so the generated collection will have documentation and examples as per the API definition file provided so you don’t have to generate documentation separately!!

And for mockserver, you can directly create a mock server from the collection as the examples are already available.

5. Publishing your documentation and adding animation to your documentation

Click the collection and click view documentation , and click publish

Now you have the documentation available in public domain for your customers.

https://swagger.io/blog/api-development/why-you-should-create-an-api-definition/

To unpublish follow the same procedure and click edit documentation and click unpublish

Adding animation:

you can add gif to your documentation , to do that use :

copy the absolute url of your gif:

provide it in documentation as :

![](https://i.pinimg.com/originals/f0/6a/9b/f06a9b257ba15f4761308ff84ab1ba2b.gif)

so when you click outside it will be resolved as

How to delete Jenkins jobs using remote access API

This is why proper API documentation and proper status code is important 😀😀😀

Spend half an hour trying to figure out how to delete a #Jenkins #job using “Jenkins remote access API” 😩 😤 😮 😱

You can access all the methods support for an endpoint say for the below job:

https://<Jenkins_url>/job/<job_name>

at : 👇

https://<Jenkins_url>/job/<job_name>/api

The documentation at this endpoint says, to programmatically delete a job, just do DELETE to “This URL”, which on clicking takes us to: 😖 😫 😩👇

https://<Jenkins_url>/job/<job_name>/

so I tried #DELETE method on : 😑 😒 👇

https://<Jenkins_url>/job/<job_name>

And guess what we get status #200 but the job never gets deleted after playing around for half an hour by reading many answers online and inspecting the #network tab when you do delete from UI. I identified the below endpoint to do this: 📌 📍 📌 📍 🚩

https://<Jenkins_url>/job/<job_name>/doDelete

But was still wondering why the documentation was wrong !!! so gave a last try of adding the front slash as per the URL opened up in the browser: 🙏🙏

DELETE https://<Jenkins_url>/job/<job_name>/

Guess what !!!!! 💰 💰 I got a status code #204 and JOB got deleted !!!! 😂 😃 😄 😅

so note: front slash is important if you are playing with Jenkins remote access API 😂 😃 😄 😅

#jenkins #devops #qaengineers #api

Passing request body multiform-data file source as variable in postman.

Issue:

In postman if we check the UI, we notice that there is no way to define file path as variable.

This looks like a limitation when we need to run file from different systems

Solution:

The solution is to hack the collection.json file. Open the json and edit the formdata src and replace it with a variable, let say fire_path so : {{fire_path}}

Now in Postman:

in pre request you can below code to set the path

pm.environment.set("file_path","C:/Users/guest/Desktop/1.png")

You can also save it as environment variable directly or pass through cmd using — env-var when using newman.

Note:

set access file from outside working directory as true (settings from top right corner)