ParseAPI One key

One key.
A whole toolkit.

Phone numbers today. Dates tomorrow. Add another lookup with the client and conventions you already know.

See it in action
parse.phone() parse.email() parse.date()

FIVE QUESTIONS. ONE PATTERN.

Change the question.

Switch APIs. Your server key stays the same, while each response answers the question you asked.

Validate and format a phone number.

Phone · JavaScript SDK
import { parseAPI } from '@parseapi/sdk';

const parse = parseAPI("YOUR_API_KEY");
const result = await parse.phone("+14155552671");
console.log(result);
Illustrative responseAPI reference ↗
{
  "phone": "+14155552671",
  "valid": true,
  "country": "US",
  "type": "unknown",
  "national": "(415) 555-2671",
  "international": "+1 415 555 2671"
}
Same YOUR_API_KEYSame parse clientProduct-specific answers

THE TOOLKIT

What will you build next?

Choose a call. See what comes back.

JavaScript SDK methods, shown without arguments. Each API page has examples, fields and plan details.

The second integration feels familiar.

01

The same way in.

Use the same server key and authentication header across the APIs available to your plan.

02

An obvious next call.

Short routes and native SDK methods keep the input in focus. Optional settings stay beside the call.

03

Familiar results and errors.

Read the fields each product documents. Handle shared API error conventions while keeping ordinary negative results as useful answers.

1server key across the toolkit
8official SDK languages
JSONthe same data over HTTP

ROOM TO BUILD

More features. Same key.

Start with a phone lookup. Add email validation, then a postal lookup. Use the same key for every API available to your plan.

Keep projects organized as you grow. Create named keys for each app and separate keys for development and production.

How keys work Find your SDK

BUILD WITH PARSEAPI

Your next feature starts here.

One setup. More useful things your application can do.

Get your API keyExplore the APIs