Skip to main content
POST
Email Lookup
Looks up the contact email for one Instagram, TikTok or YouTube creator from a profile URL. Pass profile_url; the response returns the parsed platform, the normalized profile_url, and an email object shaped {status, value}. A not_found status (with value null) is a normal result, not an error — the creator publishes no address — and is still billed as one valid lookup. Handles one creator per call. To assemble a creator list first, use post_waveinflu_similar_creators or post_waveinflu_ai_search — each match already includes an email for most creators, so call this endpoint for the ones that come back null.
Breaking change (migration to hiCreator upstream). The request field is now profile_url (previously url), and the response is data.email.{status, value} plus data.profile_url. The former emails[], contacts[], username, and quota fields have been removed. Sending the legacy url field returns 400 code=10001 and is not billed.

Example

First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. Your agent then reaches every endpoint through five tools: search, list_categories and get_details are free, use and batch_use are billed per call. Setup per client is in Connect via MCP; the live tool list and what each call costs are on aisa.one/mcp.
Set this endpoint up in your agent →

Cost and request rules

Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.001991
  • Declared unit rate (USD): 0.001991
  • Billing unit: email_lookup_point
  • Cost contract: plan_units
  • Published reference multiplier: 1.0
  • Settlement evidence source: request_snapshot

Declared request billing units

  • Units: 1

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
profile_url
string

Response

Email lookup completed

requestId
string

Request ID for support and monitoring.

Example:

"req-b6a"

billingRequestId
string

Billing reference for this call, linked to your usage log.

Example:

"7c12fbeb-1f42-4ca0-88f0-353b72ee03f2"

data
object