Email Addresses

Smart email address autocomplete. Suggests complete addresses such as jane@gmail.com or jane.smith@gmail.com. This is a client-side SDK feature: there is no /v1/email-address endpoint. The SDK calls the first-name, last-name, and email-domain endpoints and combines them.

Try it

—

Endpoint

GETSDK only (client-side)

Base URL: https://autocomplete.namedone.com

SDK Usage

emailAddresses()

1import { createClient } from "@namedone/autocomplete"
2
3const nd = createClient("nd_...")
4const { results } = await nd.emailAddresses("")

curl

1# Exchange your API key for a token
2curl -X POST https://token.namedone.com/v1 \
3  -H "Content-Type: application/json" \
4  -d '{"apiKey":"nd_..."}'
5
6# Query the email addresses endpoint
7curl "https://autocomplete.namedone.comSDK only (client-side)?token=<jwt>"

Response Format

JSON

{
  "results": [
    {
      "id": "email-address-0",
      "text": "david@gmail.com",
    }
  ],
  "query": "",
  "confidence": "low"
}

API Query Parameters

Sent as query string parameters on the HTTP request to the API.

Parameter	Type	Default	Description
token	string	—	JWT obtained from the token API. Required for authentication.

SDK Options

Passed to the SDK methods (e.g. firstNames(query, opts)). These are processed client-side and never sent to the API.

Option	Type	Default	Description
limit	number	10	Maximum number of results (1–50). Applied client-side by the SDK.
simple	boolean	false	Simplify response: deduplicate by text and strip to {text, type}.

Examples

Query:

{
  "results": [
    {
      "id": "email-address-0",
      "text": "david@gmail.com"
    },
    {
      "id": "email-address-1",
      "text": "john@hotmail.com"
    },
    {
      "id": "email-address-2",
      "text": "michael@outlook.com"
    }
  ],
  "query": "",
  "confidence": "low"
}

Query: ja

{
  "results": [
    {
      "id": "email-address-0",
      "text": "jane@gmail.com"
    },
    {
      "id": "email-address-1",
      "text": "james@hotmail.com"
    },
    {
      "id": "email-address-2",
      "text": "jack@outlook.com"
    }
  ],
  "query": "ja",
  "confidence": "low"
}

Query: jane.

{
  "results": [
    {
      "id": "email-address-0",
      "text": "jane.smith@gmail.com"
    },
    {
      "id": "email-address-1",
      "text": "jane.jones@hotmail.com"
    },
    {
      "id": "email-address-2",
      "text": "jane.williams@outlook.com"
    }
  ],
  "query": "jane.",
  "confidence": "low"
}

Query: jane@gm

{
  "results": [
    {
      "id": "email-address-0",
      "text": "jane@gmail.com"
    },
    {
      "id": "email-address-1",
      "text": "jane@gmx.com"
    }
  ],
  "query": "jane@gm",
  "confidence": "low"
}

Notes

There is no /v1/email-address endpoint. emailAddresses() combines first names, last names, and email domains in the SDK.
Empty query or a single word (no dot, no @): two requests — first names, plus the top email domains.
A trailing dot ("jane."): three requests — first names matching the prefix, top last names, and top email domains.
A name after the dot ("jane.sm"): two requests — last names matching the prefix, and top email domains.
After @ ("jane@gm"): one request — the email-domain endpoint.
The empty-query prefill runs when the field is shown. Later keystrokes follow the counts above. Usage is counted per request.
Confidence is always low. If the domain list is empty the SDK falls back to gmail.com so the field still has a suggestion.