Name parsing · Cleanup · Display formats

Name API

From a full name
to a useful contact.

Clean up names from forms, CRMs and imports. Get first, middle and last names, with titles and suffixes set aside. Add display formats for contact lists and profiles.

Get startedExplore the API

Start free. Name parsing on every plan.

Try it

Example response/name/GRACE%20HOPPER
{
  "name": "Grace Hopper",
  "valid": true,
  "prefix": null,
  "first": "Grace",
  "middle": null,
  "last": "Hopper",
  "suffix": null,
  ?deep=true
}

Full name parser

The name comes in.
The parts come back.

Handle all caps, Last, First order and attached titles. Get the clean full name, a validity check and separate fields in one call.

A clean name. Separate fields.

Turn GRACE HOPPER into Grace Hopper, with the first and last name ready for your contact record.

Request

curl "https://api.parseapi.com/name/GRACE%20HOPPER" \
  -H "X-API-Key: YOUR_API_KEY"

Example response

JSON200 OK
{
  "name": "Grace Hopper",
  "valid": true,
  "prefix": null,
  "first": "Grace",
  "middle": null,
  "last": "Hopper",
  "suffix": null
}

Full API reference

Optional Deep · Paid plans

A name that fits
your interface.

Use a short name in a contact list, a family-name-first display in a directory, or initials in an avatar. Add deep=true to the same request. Choose formatting rules with name_locale.

Contact listdeep.short
R.J. Smith
Directorydeep.directory
Smith, Robert James
Avatardeep.initials
RJS

One name. Three useful formats.

Paid Deep adds a short name, a directory name and initials, alongside available gender evidence and salutation.

Request

curl "https://api.parseapi.com/name/Robert%20James%20Smith?deep=true" \
  -H "X-API-Key: YOUR_API_KEY"

Example response

JSON200 OK
{
  "name": "Robert James Smith",
  "valid": true,
  "prefix": null,
  "first": "Robert",
  "middle": "James",
  "last": "Smith",
  "suffix": null,
  
    "gender": "male",
    "salutation": "Mr",
    "short": "R.J. Smith",
    "directory": "Smith, Robert James",
    "initials": "RJS"
  }
}

International names

Keep the name
in its own script.

Parse Unicode names, including letters with accents and combining marks. Keep mixed casing such as McIntyre, and family-name particles such as de la Hoya.

Paid Deep uses name evidence associated with 191 countries and territories, across the six scripts shown here.

Explore name handling
  • GraceLatin
  • 王Han
  • 민준Hangul
  • иванCyrillic
  • آدَمArabic
  • αγαθηGreek

From one field to your workflow

Clean names.
Where you need them.

Start with one full-name field. Save the returned parts in your CRM, fill your form fields, or clean a file of contact records.

Add to a formClean a fileBuild a CSV import

HTTP, SDKs and MCP

Copy a request above and use the same API key across ParseAPI products. Follow the reference for parameters, response fields and errors.

Name referenceChoose your SDKExplore MCP

Before you build.

Does this work with international names?

Unicode letters and combining marks are supported, including Arabic, Indic, Han, and Hangul. Splitting uses first-name-first order unless a comma marks Last, First. Paid deep matches 4,227,191 dictionary names from 191 countries and territories.

What input works?

All caps, all lower, Last, First order, and attached prefixes or suffixes. The parts come back split and proper cased.

Does casing rewrite my data?

Only all-upper or all-lower input is recased. Mixed case passes through, so McIntyre stays McIntyre.

Can I get initials and a shorter name?

Yes. Paid deep adds short, directory, and initials. Robert James Smith becomes R.J. Smith, Smith, Robert James, and RJS with the default English rules. Optional name_locale selects supported formatting rules without changing how the name is parsed. Unsupported locales return 400.

When is gender null?

Paid deep.gender is null when evidence is ambiguous, conflicting, or insufficient. Add deep=true and country=IT for Italian evidence; without country, the result uses global name evidence.

What counts as junk?

Role words, company markers like LLC, and placeholders like test test. Those answer valid: false as a 200, never a 404.

Does valid mean the person exists?

valid checks whether the input looks like a personal name. It catches supported placeholders, role words and company markers. It does not verify a person's identity or establish their gender.

What is included in each plan?

Every plan includes name cleanup, validity and the separate name parts. Paid plans add Deep with display formats, gender evidence and salutation. Both use one API request from your shared monthly allowance.

Name API pricing

Make every name useful.

One name uses one API request, including optional Deep. Your monthly allowance is shared across ParseAPI products.

Free

Start free

Name cleanup, validity and separate parts.

Room to grow

See plans

Adds Deep display formats and name evidence.

Get startedCompare plans