Domain and IP Pinger API POST

Pinger is a simple tool for checking if a URL is up. It returns a boolean value indicating whether the URL is up or not.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/pinger

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Domain and IP Pinger response payload
  }
}

About the Domain and IP Pinger API

Pinger works by analyzing the URL provided and checking if it is up. It uses various sources to determine if the URL is up and returns a boolean value indicating whether the URL is up or not.

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 Domain and IP Pinger

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 Domain and IP Pinger API.

Read the docs →

What does the Domain and IP Pinger API do?

Pinger is a simple tool for checking if a URL is up. It returns a boolean value indicating whether the URL is up or not.

How do I authenticate Domain and IP Pinger API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Domain and IP Pinger API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Domain and IP Pinger API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Domain and IP Pinger API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Domain and IP Pinger API use?

POST over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — POST /v1/pinger

Sent as JSON in the request body. 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
`host`Required	string	`google.com`	The host name or public IP that you want to ping

Optional

Parameter	Type	Example	Description
`timeout`OptionalPremium	integer	`1000`	The timeout for the ping request in milliseconds default 1500 · range 100-3000
`roundTrips`Optional	integer	`1`	How many pings to send before averaging the round-trip time default 1 · range 1-5

Example request

curl -X POST "https://api.apiverve.com/v1/pinger" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"host":"google.com","timeout":1,"roundTrips":1}'

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.
`content-type`Required	POST body	`application/json`

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 — POST /v1/pinger

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": {
    "host": "google.com",
    "numericHost": "2607:f8b0:4001:c6e::8a",
    "alive": true,
    "roundTrips": 3,
    "packetLoss": 0,
    "minMS": 0.652,
    "avgMS": 0.6846666666666666,
    "maxMS": 0.712,
    "stdDev": 0.02478350706058811,
    "times": [
      0.712,
      0.652,
      0.69
    ]
  }
}

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
`host`	string	`"google.com"`	The hostname or IP address that was pinged
`numericHost`Premium	string	`"2607:f8b0:4001:c6e::8a"`	The numeric IP address of the host that was pinged
`alive`	boolean	`true`	Whether the host is reachable and responding to ping requests
`roundTrips`	number	`3`	Number of successful ping round trips completed
`packetLoss`Premium	number	`0`	Percentage of packets lost during the ping operation
`minMS`Premium	number	`0.652`	Minimum round trip time in milliseconds
`avgMS`Premium	number	`0.6846666666666666`	Average round trip time in milliseconds
`maxMS`Premium	number	`0.712`	Maximum round trip time in milliseconds
`stdDev`Premium	number	`0.02478350706058811`	Standard deviation of round trip times
`times`Premium	array	`[0.712, ...]`	Array of individual round trip times in milliseconds

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	Domain and IP Pinger 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 — POST /v1/pinger

No SDK to install — this is a plain HTTPS call to /v1/pinger 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/pinger" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/pinger-apiSource, issues and the examples this page is built from.ReferenceDomain and IP Pinger API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/pingernpm APIVerve.API.DomainandIPPingerNuGet

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

Call it from Node.js — POST /v1/pinger

Install the Node.js SDK, then call the Domain and IP Pinger 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/pinger

Node.js

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

Resources

npm@apiverve/pingerThe published Node.js client, versioned and signed.GitHubapiverve/pinger-apiSource, issues and the examples this page is built from.ReferenceDomain and IP Pinger API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.DomainandIPPingerNuGet

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

Call it from Python — POST /v1/pinger

No SDK to install — this is a plain HTTPS call to /v1/pinger 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/pinger",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/pingernpm APIVerve.API.DomainandIPPingerNuGet

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

Call it from C# / .NET — POST /v1/pinger

Install the C# / .NET SDK, then call the Domain and IP Pinger 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.DomainandIPPinger

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/pinger");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.DomainandIPPingerThe published C# / .NET client, versioned and signed.GitHubapiverve/pinger-apiSource, issues and the examples this page is built from.ReferenceDomain and IP Pinger API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/pingernpm

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

Call it from Go — POST /v1/pinger

No SDK to install — this is a plain HTTPS call to /v1/pinger 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/pinger", 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/pingernpm APIVerve.API.DomainandIPPingerNuGet

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

Call it from PHP — POST /v1/pinger

No SDK to install — this is a plain HTTPS call to /v1/pinger 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/pinger");
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/pingernpm APIVerve.API.DomainandIPPingerNuGet

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

Call it from Ruby — POST /v1/pinger

No SDK to install — this is a plain HTTPS call to /v1/pinger 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/pinger")
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/pingernpm APIVerve.API.DomainandIPPingerNuGet

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

All articles →

API Rate Limits: What They Mean and Why You Hit ThemRate limits exist for a reason. Here's how to understand them, avoid hitting them, and handle them gracefully when you do.Read

Why Your API Integration Keeps BreakingAPIs break in production. Here's why it happens and how to build integrations that survive the real world.Read

Scalable API Architecture: Monolith to MicroservicesLearn how to design and build API architectures that scale with your business, from initial setup to handling millions of requests.Read

Domain and IP Pinger API POST

Try it — live request, no key required

About the Domain and IP Pinger API

Ways to call it

Other ways to use Domain and IP Pinger

Questions.

Request parameters — POST /v1/pinger

Required

Optional

Authentication

Response — POST /v1/pinger

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/pinger

Resources

Also published for

Call it from Node.js — POST /v1/pinger

Resources

Also published for

Call it from Python — POST /v1/pinger

Resources

Also published for

Call it from C# / .NET — POST /v1/pinger

Resources

Also published for

Call it from Go — POST /v1/pinger

Resources

Also published for

Call it from PHP — POST /v1/pinger

Resources

Also published for

Call it from Ruby — POST /v1/pinger

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Domain and IP Pinger API

Networking

Related articles

Ready to build with Domain and IP Pinger? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog