GET /v1/bloggers/by-username/
Read-only creator lookup. Returns the blogger_information row for the calling organization if the creator is currently tracked, otherwise 404 BLOGGER_NOT_TRACKED. The endpoint does not auto-track, does not enqueue, and does not call platform APIs — it is purely a DB read.
To start tracking a new creator, use POST /v1/bloggers/track first and poll GET /v1/bloggers/jobs/{job_id} until succeeded.
📋 Overview
🔐 Headers
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
📝 Request
Path Parameters
Query Parameters
Example Request
curl -X GET "https://api.influtics.com/v1/bloggers/by-username/bar.films?platform=tiktok" \
-H "Authorization: Bearer YOUR_API_KEY"
# Leading @ must be URL-encoded as %40
curl -X GET "https://api.influtics.com/v1/bloggers/by-username/%40alice?platform=youtube" \
-H "Authorization: Bearer YOUR_API_KEY"
📤 Response
200 OK — creator is tracked
{
"success": true,
"data": {
"blogger": {
"id": "b05cae01-...",
"platform": "tiktok",
"channel_username": "bar.films",
"channel_id": "MS4wLjABAAAA...",
"display_name": "Bar Films",
"avatar_url": "https://...",
"follower_count": 123456,
"is_active": true,
"last_fetched_at": "2026-08-18T22:00:00Z"
}
},
"meta": {
"processing_time_ms": 12,
"request_id": "9f7e8d4c-..."
}
}
blogger fields
⚠️ Error Responses
All errors share the standard envelope { success: false, error: { code, message, request_id, ... } }. The table below lists every documented code and the conditions that trigger it.
🔁 Migration from GET /v1/bloggers/info
The previous query-string form was removed entirely on 2026-08-20. There is no deprecation window — requests to the old path return 404 NOT_FOUND.
📌 Notes
- The endpoint charges
0credits because it does not call any platform API. - The response is scoped to the calling organization — a creator tracked by a different org returns
404 BLOGGER_NOT_TRACKED. last_fetched_atis the last time platform stats were refreshed, not the last time this endpoint was called.