# Personal Interests > Infer a person’s interests and affinities. - **Endpoint:** `POST https://api.nyne.ai/person/interests` - **Group:** Person APIs (https://api.nyne.ai/documentation/person.md) - **Auth:** `X-API-Key` + `X-API-Secret` headers - **Mode:** Asynchronous - submit returns a `request_id` (normally with `202 Accepted`); poll `GET /person/interests?request_id=` with the same auth headers until the endpoint reports a terminal response. Where supported, a `callback_url` can notify you when queued work finishes; follow this endpoint's retrieval notes. - **HTML version:** https://api.nyne.ai/documentation/person/interests Resolves a person and returns an inferred interest graph (topics, affinities, psychographic signals). At least one of `email`, `phone`, `social_media_url`, or `name` is required. Name-only lookups can match the wrong person - adding `company` and/or a social profile URL improves disambiguation. Only sections with detected signals are included in the response (possible sections: `core_profile`, `location_intelligence`, `cultural_dna`, `psychographics`, `interest_graph`, `brand_affinities`, `professional_ecosystem`, `social_graph_clusters`); empty sections are omitted, and every insight carries a `supporting_accounts` array naming the accounts that justify it. The request is queued and completes asynchronously - supply a `callback_url` or poll the status endpoint with the returned `request_id`. ## Authentication All `/person/*` and `/company/*` endpoints authenticate with an API key and secret sent as HTTP headers on every request: `X-API-Key` and `X-API-Secret`. Create keys from your Nyne.ai dashboard and keep the secret server-side. Rate limits: 100 requests/minute, 1,000 requests/hour. Full guide: https://api.nyne.ai/documentation/authentication.md ## Parameters | Name | Type | Required | Description | Example | | --- | --- | --- | --- | --- | | `email` | string | no | Email identifier. Validated for format. | "jane.doe@acme.com" | | `phone` | string | no | Phone identifier. | "+1-555-123-4567" | | `social_media_url` | string | no | Profile URL; | "https://linkedin.com/in/janedoe" | | `name` | string | no | Full name. At least one identifier (email/phone/url/name) is required. | "Jane Doe" | | `company` | string | no | Current company or workplace - disambiguates a name-based lookup. | "Acme" | | `callback_url` | string | no | If set, the completed result is POSTed here when the job finishes. Must be a valid HTTP(S) URL on an allowed host when a callback allow-list is configured. | "https://hooks.example.com/result" | ## Polling for the result A newly queued submit normally returns `202 Accepted` with a `request_id`. Poll the same path until `status` is `completed` (results stay available afterwards). Where supported, pass a `callback_url` on the submit to receive a webhook when queued work finishes; keep the documented GET as a recovery and retrieval path: ```bash curl "https://api.nyne.ai/person/interests?request_id=" \ -H "X-API-Key: YOUR_API_KEY" \ -H "X-API-Secret: YOUR_API_SECRET" ``` ## Credit usage | Item | Credits | Condition | | --- | --- | --- | | Interest Analysis | 5 | Charged on a completed analysis | | No match | 0 | Empty results never burn credits | ## Responses | Code | Meaning | | --- | --- | | `200` | Status poll result - returns the current request status and result/error fields when available | | `202` | Request queued - poll the status endpoint (or wait for the callback) with the returned request_id | | `400` | Malformed JSON, missing required parameters, or an invalid field | | `401` | Missing or invalid API credentials | | `402` | insufficient_credits - not enough credits to complete the request | | `403` | subscription_required or ip_not_allowed | | `404` | request_not_found - no matching request is available for this API key | | `429` | rate_limit_exceeded | | `503` | service_unavailable - the API is temporarily unavailable | ## Example request ### cURL ```bash curl -X POST https://api.nyne.ai/person/interests \ -H "X-API-Key: YOUR_API_KEY" \ -H "X-API-Secret: YOUR_API_SECRET" \ -H "Content-Type: application/json" \ -d '{ "social_media_url": "https://linkedin.com/in/janedoe" }' ``` ### Python ```python import requests resp = requests.post( "https://api.nyne.ai/person/interests", headers={ "X-API-Key": "YOUR_API_KEY", "X-API-Secret": "YOUR_API_SECRET", }, json={ "social_media_url": "https://linkedin.com/in/janedoe", }, ) data = resp.json() print(data) ``` ### Node ```javascript const resp = await fetch("https://api.nyne.ai/person/interests", { method: "POST", headers: { "X-API-Key": "YOUR_API_KEY", "X-API-Secret": "YOUR_API_SECRET", "Content-Type": "application/json", }, body: JSON.stringify({ social_media_url: "https://linkedin.com/in/janedoe", }), }); const data = await resp.json(); console.log(data); ``` ### PHP ```php true, CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => [ "X-API-Key: YOUR_API_KEY", "X-API-Secret: YOUR_API_SECRET", "Content-Type: application/json", ], CURLOPT_POSTFIELDS => json_encode([ "social_media_url" => "https://linkedin.com/in/janedoe", ]), ]); $data = json_decode(curl_exec($ch), true); print_r($data); ``` ## Example response ```json { "request_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4_1717000000_4271", "status": "completed", "completed": true, "result": { "core_profile": { "archetypes": [ "Tech Leader", "Thought Leader" ], "supporting_accounts": [ "@techcrunch", "@ycombinator" ] }, "interest_graph": { "technology": { "interests": [ { "topic": "Machine Learning", "supporting_accounts": [ "@exampleai" ] } ] }, "sports_and_fitness": { "interests": [ { "activity": "Running", "supporting_accounts": [ "@strava" ] } ] } }, "brand_affinities": [ { "category": "Cloud Platforms", "brands": [ "AWS", "Google Cloud" ] } ], "professional_ecosystem": { "industry_focus": [ "SaaS", "Developer Tools" ], "supporting_accounts": [ "@github", "@stripe" ] }, "following_count": 2847 }, "completed_on": "2026-01-15T10:31:00Z" } ``` --- All documentation pages are available as Markdown by appending `.md` to their URL. Index: https://api.nyne.ai/llms.txt