GET/desearch/people/profiles

List the people your searches found

Everyone your searches on one platform found, one entry per person: their best-scoring result and the search behind it (`found_by`). Search by name, handle, bio or location, filter by what people have (`has=email,instagram`), audience, fit score, location or verification, and sort by score, most recent or audience. Searches whose results expired (30 days after they ended) are left out. Free. Billing metadata: successful billable responses include the `X-Desearch-Cost-Usd`, `X-Desearch-Usage-Count`, `X-Desearch-Service`, and `X-Desearch-Currency` headers. JSON object responses also include optional `cost_usd`, `usage_count`, `service`, and `currency` fields. For example, `usage_count=10` at `$0.015 / 1,000` resolves to `cost_usd=0.00015`. JSON arrays, text, and streaming responses keep their body shape and expose billing metadata only through headers.

Base URL

https://api.desearch.ai

Implementation guidance

Use List the people your searches found when your application needs scored public profiles of people and creatorswithout maintaining its own crawler, social-data pipeline, or retrieval infrastructure. The endpoint returns structured data that can be consumed by agents, research tools, dashboards, and retrieval-augmented generation workflows. Keep the request focused on the minimum fields your workflow needs so responses remain fast and easy to validate.

Send requests to GET /desearch/people/profiles with your Desearch API key in the authorization header. Treat the key as a server-side secret, validate all required parameters before sending the request, and handle non-2xx responses explicitly. Production integrations should use sensible timeouts, retry only transient failures with backoff, and record the response status and request identifier for troubleshooting.

Test the example request below before integrating it into a larger workflow. Confirm that the returned fields, links, and timestamps meet your freshness requirements, then add schema validation at the application boundary. For agentic systems, preserve source URLs with the generated answer so users can inspect evidence and your application can avoid presenting unsupported claims.

Query Parameters

platformstringrequired

x, youtube, linkedin or tiktok

qstring

Text in the name, handle, bio or location

sortstring

score, recent or audience

Default: score

limitinteger

Default: 50

cursorstring

next_cursor from the previous page

hasstring

Comma-separated channels every person must have: email, website, x, linkedin, instagram, youtube, tiktok

min_audiencestring

Minimum followers (subscribers on YouTube)

max_audiencestring

Maximum followers (subscribers on YouTube)

min_scorestring

Minimum fit score

locationstring

Text in the location, e.g. 'united states'

verifiedstring

Only verified accounts (X and TikTok)

Responses

200Successful Response

400Bad request: an unknown platform, sort, status, cursor or `has` channel, or a filter the platform does not support

401Unauthorized

422Validation Error

500Internal Server Error

Authorization

Your API key is sent in the Authorization header.

Request

curl -X GET "https://api.desearch.ai/desearch/people/profiles" \
  -H "Authorization: YOUR_API_KEY" \
  -H "Content-Type: application/json"

ResponseSchema

{
  "profiles": [
    {
      "id": "Id",
      "platform": "x",
      "handle": "Handle",
      "url": "string",
      "name": "string",
      "avatar_url": "string",
      "bio": "string",
      "location": "string",
      "metrics": {},
      "links": [
        {}
      ],
      "contacts": [
        {}
      ],
      "evidence": [
        {
          "type": "Type",
          "url": "string",
          "text": "string",
          "title": "string",
          "published_at": "string",
          "metrics": {}
        }
      ],
      "score": {
        "value": 0,
        "qualified": true,
        "summary": "string",
        "matched_signals": [
          "string"
        ],
        "profile_fit": [
          "string"
        ],
        "buying_triggers": [
          "string"
        ],
        "evidence": [
          "string"
        ],
        "reasons": [
          "string"
        ],
        "concerns": [
          "string"
        ]
      },
      "attributes": {},
      "found_by": {
        "task_id": "Task Id",
        "query": "Query",
        "found_at": "2024-01-15T10:30:00Z",
        "times_found": 0
      }
    }
  ],
  "total": 0,
  "next_cursor": "string"
}

Possible status codes:

200401422429500