Port Number Lookup API Reference

Overview

Port Number Lookup works by querying a database of well-known and registered ports including HTTP, HTTPS, FTP, SSH, databases, and more. Supports lookup by port number or service name with detailed protocol information.

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/portnumberlookup

curl "https://api.apiverve.com/v1/portnumberlookup?port=443" \
  -H "x-api-key: your_api_key_here"

const res = await fetch('https://api.apiverve.com/v1/portnumberlookup?port=443', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

import requests

res = requests.get(
    "https://api.apiverve.com/v1/portnumberlookup?port=443",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/portnumberlookup?port=443", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

Parameter	Type	Description
`port`Required	integer	Port number to lookup range 1–65535

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "count": 1,
    "ports": [
      {
        "port": 443,
        "service": "HTTPS",
        "protocol": "TCP",
        "description": "HTTP Secure (HTTP over TLS/SSL)",
        "category": "Web",
        "is_well_known": true,
        "is_registered": false,
        "is_dynamic": false
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`count`	number	`1`	Number of matching ports returned
`ports`	array[1]		The matching port registrations
`port`	number	`443`	Port number
`service`	string	`"HTTPS"`	Service name for this port
`protocol`Premium	string	`"TCP"`	Protocol (TCP/UDP)
`description`	string	`"HTTP Secure (HTTP over TLS/SSL)"`	Description of the service
`category`Premium	string	`"Web"`	Port category (well-known, registered)
`is_well_known`	boolean	`true`	Whether the port is in the well-known range, 0 to 1023
`is_registered`	boolean	`false`	Whether the port is in the registered range, 1024 to 49151
`is_dynamic`	boolean	`false`	Whether the port is in the dynamic or ephemeral range, 49152 and above

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted	A key restriction or IP allow-list; see key scoping.
`429`	Rate limited, or out of credits	Read `error` to tell them apart; see rate limits.

Use cases

Network Configuration: Identify services and configure firewall rules based on port numbers
Security Auditing: Analyze open ports and identify running services during security assessments
Troubleshooting: Diagnose network connectivity issues by identifying services on specific ports
Documentation: Generate network documentation and service inventories with port information

Other ways to use Port Number Lookup

Set up Port Number Lookup on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

Port Number Lookup