Data endpoint · 1 credit

Creator profile

Fetch one directory record by its pk (returned by search). The response is the full stored record.

GET /v1/creators/{pk}

Example

request

curl "https://api.ugcroster.com/v1/creators/189352" \
  -H "Authorization: Bearer rsk_your_key_here"

response 200

{
  "data": {
    "pk": 189352,
    "username": "…",
    "full_name": "…",
    "follower_count": 48210,
    "engagement_rate": 0.041,
    "category": "Beauty",
    "biography": "…",
    "niches": ["skincare"],
    "extracted_email": "…@…",
    "city": "Austin", "state": "TX", "country": "US",
    "external_url": "https://…",
    "is_verified": false,
    "age": 27,
    "gender": "female"
  }
}

Errors

A non-numeric pk returns 422 VALIDATION_ERROR; an unknown one returns 404 NOT_FOUND. Not-found reads still cost 1 credit. Validate pks from search results rather than probing.

Caching

Responses carry Cache-Control: public, s-maxage=600. Records do not change minute to minute; caching reads on your side for at least 10 minutes is safe and saves credits.