Postman Collection for Dijets Node

What Is Postman?#

Postman is a free tool used by developers to quickly and easily send REST, SOAP, and GraphQL requests and test APIs. It is available as both an online tool and an application for Linux, MacOS and Windows. Postman allows you to quickly issue API calls and see the responses in a nicely formatted, searchable form.

We have made a Postman collection for Dijets, that includes all the public API calls that are available on DijetsNodeGo instance allowing you to quickly issue commands to your node and see the response, without having to copy and paste long and complicated curl commands.

Along with the API collection, there is also an example Dijets environment for Postman, that defines common variables such as IP address of the node, your Dijets addresses and similar common elements of the queries, so you don't have to enter them multiple times.

Combined, they will allow you to easily keep tabs on your node, check on its state and do quick queries to find out details about its operation.

Setup#

Postman Installation#

Postman can be installed locally or used as a web app. We recommend installing the application, as it simplifies operation. You can download Postman from its website. It is recommended that you sign up using your email address as then your workspace can be easily backed up and shared between web app and the app installed on your computer.

After you installed the application, run it. It will prompt you to create an account or log in. Do so. Again, it is not necessary, but recommended.

Collection Import#

Select New workspace from Workspaces tab and follow the prompts to crate a new workspace. This will where the rest of the work will be done.

We're ready to import the collection. On the header of the Workspaces tab select New and switch to Link tab.

There, in the URL input field paste the link to the collection:

Postman will recognize the format of the file content and offer to import the file as a collection. Complete the import. Now you will have Dijets collection in your Workspace.

Environment Import#

Next, we have to import the environment variables. Again, the header of the Workspaces tab select New and switch to Link tab. this time, paste the link to the environment JSON:

Postman will recognize the format of the file:

Import it to your workspace. Now, we will need to edit that environment to suit the actual parameters of your particular installation. These are the parameters that differ from the defaults in the imported file.

Click the eye icon next to the environment dropdown:

Select the Edit button to change the defaults. As a minimum, you will need to change the IP address of your node, which is the value of the host variable. Change it to the IP of your node (change both the initial and current values). Also, if your node is not running on the same machine where you installed Postman, make sure your node is accepting the connections on the API port from the outside by checking the appropriate command line option.

Now we sorted everything out, and we're ready to query the node.

Making API Calls#

Open one of the API call groups, for example Health. Double-click health call:

You will see that format of the call uses the http, host and port environment variables. Click Send. Request will be sent, and soon you will see the response, in the Body tab in the Response:

To see the actual call and the variables that are sent to the node, switch to Body tab in the API call tabs. There you can quickly change the variables to see the response to different queries.

Conclusion#

If you completed the tutorial, you are now able to quickly issue API calls to your node without messing with the curl commands in the terminal. This allows you to quickly see the state of your node, track changes or double-check the health or liveness of your node.

Contributing#

We're hoping to continuously keep this collection up-to-date with the Dijets APIs.

If you're able to help improve the Dijets Postman Collection in any way, first create a feature branch by branching off of master, next make the improvements on your feature branch and then create a pull request to merge your work back in to master.

If you have any other questions or suggestions, join us on Qowalts.