Introduction
The Person Profile Live endpoint triggers a real-time fetch of a Social profile. Instead of relying on cached data, it pulls a fresh copy and returns the result asynchronously.
Use this endpoint when you need the most up-to-date profile data and can wait for the async result. Retrieve the result via polling (recommended, no public endpoint required) or via a webhook callback (advanced, push delivery).
Note
Async, not real-time. We aim to deliver each result in under 15 seconds, but it can take tens of minutes depending on conditions. Built to update databases and feed async pipelines, not to back a synchronous request a user is waiting on. See Polling for delivery details.
Important
Not available on the free trial. This endpoint requires an active pay-as-you-go balance or an Enterprise plan. Add credits to your workspace to unlock it, or contact sales to discuss Enterprise pricing.
Authorization
apikey
string
required
Authorization: Bearer YOUR_API_KEY header.Request body
url
string
required
https://social.com/in/janedoe)webhookUrl
string
Response structure
This endpoint replies immediately with a webhookId. You then have two ways to retrieve the actual result:
- Polling (recommended). Call
GET /v2/webhooks/:webhookIduntil the status issucceeded. No webhook URL needed. See the Polling guide. - Webhook callback (advanced). If you provided a
webhookUrl(or a workspace default is configured), the gateway POSTs the person data to that URL once the fetch completes. See Webhook callback payload (advanced) below.
success
boolean
true if the job was created successfullyerror
null
null on successWebhook callback payload (advanced)
Once the live fetch completes, the gateway POSTs a JSON payload to your webhookUrl. Use the webhookId from the initial response to correlate the callback with your original request.
The payload is not wrapped in an envelope (no success, error, metadata, or quotas keys at the top level, unlike the synchronous response).
webhookId
string
Webhook callback errors (advanced)
When the live fetch fails, data does not contain the profile fields. Instead, it contains the original input echoed back together with an errorCode identifying the failure reason:
{
"webhookId": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
"data": {
"url": "https://www.social.com/in/janedoe",
"errorCode": "data-not-found"
}
}
data.errorCode will be one of the following values:
| Code | Billed | Description |
|---|---|---|
person-not-found |
Yes | The person profile doesn’t exist or could not be scraped |
invalid-data |
No | The fetched data failed quality validation |
fetch-data-error |
No | The API failed while fetching data. Safe to retry |
result-unavailable |
No | The enrichment completed but the result was lost on our side. Retry the job. If the request was charged, contact support to get the credit back. |
Note
Billed means the credits consumed at request time are kept. Not billed means the credits are fully refunded to your workspace balance.