Skip to content

Commit 059289d

Browse files
authored
fix spacing on nmap api guide (#109)
2 parents f990a9a + 174ccba commit 059289d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

pages/api/Using_with_nmap.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords: postman, swagger, docs, requests, nmap
55
last_updated: september, 2020
66
summary: "How to capture Nmap output in the Tidal Migrations API"
77
sidebar: main_sidebar
8-
permalink: nmap_api.html
8+
permalink: nmap-api.html
99
---
1010

1111
You can send the output generated by Nmap to the Tidal Migrations API in two ways. First, by using Tidal Tools [Instructions](https://guides.tidalmg.com/host-discovery.html) and second, by sending the data to the API by using a service like Postman.
@@ -25,11 +25,11 @@ This is the shape of the expected payload.
2525

2626
```
2727
{
28-
"nmap_output": {
29-
"hosts": [
30-
{
28+
"nmap_output": {
29+
"hosts": [
30+
{
3131
"ip_address" : "32.199.2.33",
32-
"ptr_record": "abc-32-199-2-33.cloudfront.net",
32+
"ptr_record": "abc-32-199-2-33.cloudfront.net",
3333
"ports": [
3434
{
3535
"port": 22,

0 commit comments

Comments
 (0)