URL Title API

POST

Extract HTML page titles from any URL without scraping.

URL Title fetches the HTML title tag of any web page in real time from a target URL. Paid plans also retrieve an array of every H1 heading tag found on the page.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/urltitle

Body

urlstring

Verification

Format

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

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "title": "HTML element - Wikipedia",
    "h1": [
      "HTML element"
    ]
  }
}

About the URL Title API

Send a web address to parse the live document over HTTP. The endpoint inspects the markup and extracts the text content inside the title tag. On paid tiers, the response also includes a list of all H1 headings located within the page body.

What people use it for

Bookmark Link Cards: Social bookmarking platforms generate readable cards by pulling page titles whenever members save external web links.
SEO Metadata Auditing: Audit web pages across a client domain to verify that HTML title tags exist and match target requirements.
Reading List Management: When readers submit articles to an aggregator, the system attaches live page titles to label each entry automatically.
Chat Message Previews: Messaging services parse shared URLs on post to show clear discussion context before members click outbound links.

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 URL Title

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 URL Title API.

Read the docs →

What kinds of URLs can I pass to the API?

You can pass any standard web page URL. The API accepts any public web address as a string parameter and inspects the page in real time to locate its HTML title tag.

Can I extract H1 headings on the Free plan?

No. The HTML title is included on every tier, but H1 headings are a premium field reserved for paid plans. Upgrading to Starter or above unlocks the array of all H1 heading elements found on the page.

What would checking 10,000 URLs a month cost me?

Checking 10,000 URLs uses 100,000 credits, which uses half of the Starter plan allowance of 20,000 calls per month. That works out to about $1.50 per 1,000 calls. The Free plan includes 20 calls each month to test with.

What happens if a web page has multiple H1 headings?

URL Title returns them all. On paid plans, the H1 response field delivers an array containing every H1 element discovered on the target page, rather than only the first one. If a page contains no H1 elements, the array returns empty.

Can I use the extracted titles inside my commercial app?

Yes, as long as you subscribe to a paid plan. You can display page titles and headings inside your own application, link previewer, or bookmark tool. You may not resell or redistribute the raw metadata as a standalone dataset.

Request parameters — POST /v1/urltitle

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
`url`Required	string	`https://en.wikipedia.org/wiki/HTML_element`	The URL of the web page to get the title of url

Example request

curl -X POST "https://api.apiverve.com/v1/urltitle" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://en.wikipedia.org/wiki/HTML_element"}'

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/urltitle

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": {
    "title": "HTML element - Wikipedia",
    "h1": [
      "HTML element"
    ]
  }
}

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
`title`	string	`"HTML element - Wikipedia"`	The HTML title tag content of the web page
`h1`Premium	array	`[HTML element]`	Array of all H1 heading elements found on the page

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 — 10 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	URL Title calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

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/urltitle

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

Resources

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

Also published for

@apiverve/urltitlenpm apiverve-urltitlePyPI APIVerve.API.URLTitleNuGet

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/urltitle

Install the Node.js SDK, then call the URL Title 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/urltitle

Node.js

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

Resources

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

Also published for

apiverve-urltitlePyPI APIVerve.API.URLTitleNuGet

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

Call it from Python — POST /v1/urltitle

Install the Python SDK, then call the URL Title API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-urltitle

Python

import requests

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

Resources

PyPIapiverve-urltitleThe published Python client, versioned and signed.GitHubapiverve/urltitle-apiSource, issues and the examples this page is built from.ReferenceURL Title API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/urltitlenpm APIVerve.API.URLTitleNuGet

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/urltitle

Install the C# / .NET SDK, then call the URL Title 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.URLTitle

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

Resources

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

Also published for

@apiverve/urltitlenpm apiverve-urltitlePyPI

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

Call it from Go — POST /v1/urltitle

No SDK to install — this is a plain HTTPS call to /v1/urltitle 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/urltitle", 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/urltitlenpm apiverve-urltitlePyPI APIVerve.API.URLTitleNuGet

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

Call it from PHP — POST /v1/urltitle

No SDK to install — this is a plain HTTPS call to /v1/urltitle 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/urltitle");
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/urltitlenpm apiverve-urltitlePyPI APIVerve.API.URLTitleNuGet

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

Call it from Ruby — POST /v1/urltitle

No SDK to install — this is a plain HTTPS call to /v1/urltitle 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/urltitle")
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/urltitlenpm apiverve-urltitlePyPI APIVerve.API.URLTitleNuGet

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

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read

WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read

URL Title API

Try it — live request, no key required

About the URL Title API

What people use it for

Ways to call it

Other ways to use URL Title

Questions.

Request parameters — POST /v1/urltitle

Required

Authentication

Response — POST /v1/urltitle

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — POST /v1/urltitle

Resources

Also published for

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

Resources

Also published for

Call it from Python — POST /v1/urltitle

Resources

Also published for

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

Resources

Also published for

Call it from Go — POST /v1/urltitle

Resources

Also published for

Call it from PHP — POST /v1/urltitle

Resources

Also published for

Call it from Ruby — POST /v1/urltitle

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — URL Title API

Domain Data

Related articles

Ready to build with URL Title? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog