Human Name Parser API
Overview
To use Human Name Parser, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/humannameparserExample
How to call the Human Name Parser API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/humannameparser?name=MR.%20MARTINO%20PETROS%20DE%20FLORENCE%20(TINO)%20Jr." \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/humannameparser?name=MR.%20MARTINO%20PETROS%20DE%20FLORENCE%20(TINO)%20Jr.', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/humannameparser?name=MR.%20MARTINO%20PETROS%20DE%20FLORENCE%20(TINO)%20Jr.', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/humannameparser?name=MR.%20MARTINO%20PETROS%20DE%20FLORENCE%20(TINO)%20Jr.", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"name": "MR. MARTINO PETROS DE FLORENCE (TINO) Jr.",
"parsed": {
"title": "Mr.",
"first": "Martino",
"middle": "Petros",
"last": "de Florence",
"nick": "Tino",
"suffix": "Jr."
},
"initials": "MPF",
"formalName": "Mr. de Florence, Martino P. Jr."
}
}Authentication
The Human Name Parser API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Human Name Parser API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Human Name Parser API:
Parse Human Name
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
name | string | required | The human name to parse | - |
Response
The Human Name Parser API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<name>MR. MARTINO PETROS DE FLORENCE (TINO) Jr.</name>
<parsed>
<title>Mr.</title>
<first>Martino</first>
<middle>Petros</middle>
<last>de Florence</last>
<nick>Tino</nick>
<suffix>Jr.</suffix>
</parsed>
<initials>MPF</initials>
<formalName>Mr. de Florence, Martino P. Jr.</formalName>
</data>
</response>
status: ok
error: null
data:
name: MR. MARTINO PETROS DE FLORENCE (TINO) Jr.
parsed:
title: Mr.
first: Martino
middle: Petros
last: de Florence
nick: Tino
suffix: Jr.
initials: MPF
formalName: Mr. de Florence, Martino P. Jr.
| key | value |
|---|---|
| name | MR. MARTINO PETROS DE FLORENCE (TINO) Jr. |
| parsed | {title:Mr.,first:Martino,middle:Petros,last:de Florence,nick:Tino,suffix:Jr.} |
| initials | MPF |
| formalName | Mr. de Florence, Martino P. Jr. |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
name | string | The original human name provided for parsing | |
parsed | object | - | |
â”” title | string | Title or prefix extracted from the name (e.g., Mr., Mrs.) | |
â”” first | string | First name component of the parsed name | |
â”” middle | string | Middle name component of the parsed name | |
â”” last | string | Last name or surname component of the parsed name | |
â”” nick | string | Nickname or preferred name extracted from parentheses | |
â”” suffix | string | Suffix or post-nominal letters (e.g., Jr., Sr., PhD) | |
initials | string | Initials derived from first, middle, and last name | |
formalNamePremium | string | Formally formatted name (Title Last, First M. Suffix) |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Human Name Parser through GraphQL to combine it with other API calls in a single request. Query only the human name parser data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
humannameparser(
input: {
name: "MR. MARTINO PETROS DE FLORENCE (TINO) Jr."
}
) {
name
parsed {
title
first
middle
last
nick
suffix
}
initials
formalName
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Human Name Parser API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Human Name Parser requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Human Name Parser API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Human Name Parser
Official Human Name Parser packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Human Name Parser works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Human Name Parser?
How many credits does Human Name Parser cost?
Each successful Human Name Parser API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful human name parser lookups.
Can I use Human Name Parser in production?
The free plan is for testing and development only. For production use of Human Name Parser, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Human Name Parser from a browser?
What happens if I exceed my Human Name Parser credit limit?
When you reach your monthly credit limit, Human Name Parser API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








