Nyne.ai API Login
API Reference

Person Data API Reference

Resolve anyone from any identifier - then enrich, monitor, and analyze them. Search, verified contact data, social intelligence, and AI research over the same person graph.

21 endpoints X-API-Key + X-API-Secret Async - poll or webhook

Every Person API starts from the same idea: give us whatever you have - an email address, a phone number, a social profile URL, or just a name and company - and Nyne.ai resolves it to a real person. From there each endpoint returns a different slice of that person: a full merged profile, a verified work email or mobile number, their social accounts and recent posts, or an AI-generated dossier.

All endpoints are asynchronous POST requests: the submit returns 202 Accepted with a request_id, and you poll the same path - GET <path>?request_id=… - until status is completed, or supply a callback_url to receive the result by webhook instead.

Credits are charged only on meaningful results - an empty result never burns credits. Per-result options (verified emails, phone numbers, AI scoring) carry their own line items, listed on each endpoint's page.

Endpoints

Find people

Start from intent instead of an identifier - a natural-language query, keywords, or a triggering event.

Enrichment & contact data

Turn an identifier into a full profile - or exactly the fields you need, like a verified email or mobile.

Social intelligence

Map a person's social presence: every account, recent posts, who they engage with, and whether an account is real.

AI research & analysis

Let the platform read everything for you - research dossiers, interest graphs, press coverage, AI Q&A, and persona simulation.

Worked example

The flagship endpoint, Person Enrichment, shows the request/poll shape every async Person API shares. Submit any identifier, get a request_id back immediately, then poll the same path for the merged profile - usually ready in under a second.

1. Submit - POST /person/enrichment

curl -X POST https://api.nyne.ai/person/enrichment \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "name": "Jane Doe",
    "company": "Acme",
    "newsfeed": [
      "linkedin",
      "github"
    ],
    "ai_enhanced_search": true
  }'

The call returns 202 Accepted immediately:

{
  "request_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4_1717000000_4271",
  "status": "queued"
}

2. Poll until completed

curl "https://api.nyne.ai/person/enrichment?request_id=<request_id>" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-API-Secret: YOUR_API_SECRET"

When status is completed, the same response carries the result:

{
  "request_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4_1717000000_4271",
  "status": "completed",
  "completed": true,
  "result": {
    "displayname": "Jane Doe",
    "firstname": "Jane",
    "lastname": "Doe",
    "headline": "VP of Product at Acme",
    "location": "San Francisco, CA",
    "best_business_email": "[email protected]",
    "best_work_email": "[email protected]",
    "best_personal_email": "[email protected]",
    "altemails": [
      "[email protected]",
      "[email protected]"
    ],
    "fullphone": [
      {
        "fullphone": "+1-555-123-4567",
        "phone_type": "mobile"
      }
    ],
    "social_profiles": {
      "linkedin": {
        "url": "https://linkedin.com/in/janedoe",
        "followers": 2847
      },
      "twitter": {
        "url": "https://x.com/janedoe",
        "followers": 1234
      }
    },
    "organizations": [
      {
        "name": "Acme",
        "title": "VP of Product",
        "is_current": true
      },
      {
        "name": "StartupXYZ",
        "title": "Product Manager",
        "is_current": false
      }
    ],
    "classifications": {
      "seniority": [
        "vp"
      ],
      "job_functions": [
        "product_management"
      ],
      "employment_types": [
        "full_time"
      ]
    },
    "total_experience_years": 12
  },
  "error": null,
  "created_on": "2026-01-15T10:34:21",
  "completed_on": "2026-01-15T10:35:00"
}
Skip polling with a webhook
Every async endpoint accepts a callback_url - the completed result is POSTed there when the job finishes, so you never poll at all.
Authentication & credits

Every endpoint here authenticates with an API key + secret sent as HTTP headers (X-API-Key · X-API-Secret) - create them from your dashboard and see the Authentication guide for rate limits and IP locking. Each endpoint page lists its exact credit costs.

Credits are charged on results
Empty results never burn credits. Per-result options (verified emails, phone numbers, AI scoring) carry their own line items - check the Credit usage table on each endpoint page.
FAQ

Which Person API should I start with?

Use Person Enrichment when you already have an identifier, People Search when you need to find people from criteria, and Lookup Fields when you only want selected fields such as emails, phones, work history, or social profiles.

Can the Person APIs return contact data?

Yes. Person Enrichment, Lookup Fields, Work Email Lookup, and Phone Number Lookup can return contact fields when the data is available and permitted for your use case.

How do async Person API requests work?

Submit a POST request and store the returned request_id, then poll the same endpoint with that request_id or provide a callback_url to receive the completed result by webhook.