Port Number Lookup API

GET

Resolve any port number to its assigned network service.

Port Number Lookup identifies network services and port ranges from any port number or service name. Each query returns the assigned service, description, and classification across well-known, registered, or dynamic ranges, while paid plans add protocol details.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/portnumberlookup?port=443

Query parameters

portinteger

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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
      }
    ]
  }
}

About the Port Number Lookup API

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.

What people use it for

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

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Port Number Lookup

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Port Number Lookup API.

Read the docs →

Can I search by service name instead of port number?

Yes. You can query by either an integer port number or a service name string. A service lookup returns all matching port numbers registered to that service, along with their descriptions and range classifications.

How many port lookups does the Free plan cover?

The Free plan includes 100 lookups each month at 2 credits per call. On the Starter plan, 200,000 credits cover 100,000 lookups per month, which works out to about $0.30 per 1,000 calls.

Are protocol and category details included on the Free plan?

No. The Free plan returns the port number, service name, description, and range classifications. Transport protocols like TCP or UDP and category tags require any paid plan, starting with Starter.

How fresh is the port directory data?

The Port Number Lookup database catalogs 65,000 ports and receives monthly updates. It covers the full range of well-known, registered, and dynamic port assignments.

Can I display port metadata inside a commercial security tool?

Yes, as long as you subscribe to any paid plan. You can integrate the port and service data directly into your own product or security audit reports, but you may not resell or redistribute the raw dataset as-is.

Request parameters — GET /v1/portnumberlookup

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`port`Required	integer	`443`	Port number to lookup range 1-65535

Example request

1
2

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

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

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.

Response — GET /v1/portnumberlookup

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

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

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Port Number Lookup calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/portnumberlookup

No SDK to install — this is a plain HTTPS call to /v1/portnumberlookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/portnumberlookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/portnumberlookup-apiSource, issues and the examples this page is built from.ReferencePort Number Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/portnumberlookupnpm APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/portnumberlookup

Install the Node.js SDK, then call the Port Number Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/portnumberlookup

Node.js

const res = await fetch("https://api.apiverve.com/v1/portnumberlookup", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/portnumberlookupThe published Node.js client, versioned and signed.GitHubapiverve/portnumberlookup-apiSource, issues and the examples this page is built from.ReferencePort Number Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/portnumberlookup

No SDK to install — this is a plain HTTPS call to /v1/portnumberlookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/portnumberlookup",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/portnumberlookupnpm APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/portnumberlookup

Install the C# / .NET SDK, then call the Port Number Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.PortNumberLookup

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/portnumberlookup");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.PortNumberLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/portnumberlookup-apiSource, issues and the examples this page is built from.ReferencePort Number Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/portnumberlookupnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/portnumberlookup

No SDK to install — this is a plain HTTPS call to /v1/portnumberlookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/portnumberlookup", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/portnumberlookupnpm APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/portnumberlookup

No SDK to install — this is a plain HTTPS call to /v1/portnumberlookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/portnumberlookup");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/portnumberlookupnpm APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/portnumberlookup

No SDK to install — this is a plain HTTPS call to /v1/portnumberlookup with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/portnumberlookup")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/portnumberlookupnpm APIVerve.API.PortNumberLookupNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

API Rate Limiting Done Right: A Complete GuideLearn how to design rate limits that protect your API while maintaining good developer experience.Read

Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Port Number Lookup API

Try it — live request, no key required

About the Port Number Lookup API

What people use it for

Ways to call it

Other ways to use Port Number Lookup

Questions.

Request parameters — GET /v1/portnumberlookup

Required

Authentication

Response — GET /v1/portnumberlookup

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/portnumberlookup

Resources

Also published for

Call it from Node.js — GET /v1/portnumberlookup

Resources

Also published for

Call it from Python — GET /v1/portnumberlookup

Resources

Also published for

Call it from C# / .NET — GET /v1/portnumberlookup

Resources

Also published for

Call it from Go — GET /v1/portnumberlookup

Resources

Also published for

Call it from PHP — GET /v1/portnumberlookup

Resources

Also published for

Call it from Ruby — GET /v1/portnumberlookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Port Number Lookup API

Reference Data

Related articles

Ready to build with Port Number Lookup? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog