ParseAPI Clean input

Messy in.
Useful out.

People bring spaces, punctuation, different formats and the occasional typo. Your app needs something it can use.

See it in action

Smith, John John Smith

START WITH WHAT YOU HAVE

A little messy is normal.

Choose an example. See what becomes a clean value, what becomes a field, and what stays a suggestion.

Illustrative responses

YOUR INPUT

Smith, John

John Smith

Recognize the last-name-first format. Get a clean name and separate fields ready for your form or database.

See the name reference

GET/name/Smith,%20John

{
  "name": "John Smith",
  "valid": true,
  "prefix": null,
  "first": "John",
  "middle": null,
  "last": "Smith",
  "suffix": null
}

Useful, from the first field.

A name can become a greeting. An IBAN can be ready to compare. An email typo can become a helpful question. The structure is what makes the input useful.

Ready to store.

Normalized values make comparison and reuse simpler. Keep a readable format where the product provides one.

Ready to build with.

Separate fields give your app the first name, country or identifier it needs without parsing a display string again.

You keep the decision.

An email correction is a separate suggestion. Your app can ask the person to confirm it before using it.

A LITTLE CONTEXT

Bring what you know.

A country hint can complete an IBAN that arrives without its country prefix. An existing prefix keeps its meaning.

Add the country you already know

curl "https://api.parseapi.com/iban/89370400440532013000?country=DE" \
  -H "X-API-Key: YOUR_API_KEY"

Different inputs need different context. Each API documents the formats and hints it accepts.

Explore IBAN inputs

BUILD WITH PARSEAPI

Start with real input.

Get useful fields back. Put them to work.

Get your API key Try the free tools