My Info V4
Returns basic information about the current API key owner.
Useful for quickly checking which account an API key is bound to. Handy for initial integration debugging or key validation.
Request Parameters
-
Authorization: HeaderHashScraper API key. Send it in the form
Bearer <api_key>. You can create several keys on the API & Integrations page; a read-only key works only for GET requests (others return HTTP 403INSUFFICIENT_SCOPE). An extra key stops working after the expiry date you chose when creating it and is refused with HTTP 401, like a key that is turned off (the default key never expires).
Response Fields
-
result: StringResult of the request.
-
version: StringAPI version.
-
request_id: StringRequest trace ID. Echoed from the client's
X-Request-IDheader when it starts withreq_, otherwise generated by the server (req_<uuid>). -
elapsed_sec: FloatTime the server took to produce the response, in seconds (Float).
-
data: ObjectCurrent user info.
-
email: StringUser email.
-
name: StringUser name.
-
Error Responses
-
MISSING_API_KEY
{ "result": "error", "version": "v4", "request_id": "req_5a8c1f1c-...", "code": "MISSING_API_KEY", "message": "API key is missing.", "elapsed_sec": 0.0008, "details": { "hint": "Send `Authorization: Bearer <api_key>` header." } } -
INVALID_API_KEY
{ "result": "error", "version": "v4", "request_id": "req_5a8c1f1c-...", "code": "INVALID_API_KEY", "message": "API key is invalid.", "elapsed_sec": 0.0011 }
Related Guides
Example Request
Example Response 200
{
"result": "success",
"version": "v4",
"request_id": "req_5a8c1f1c-9b2d-4e7c-9abf-3f7e0a4d1b21",
"elapsed_sec": 0.0011,
"data": {
"email": "dev@example.com",
"name": "Sample User"
}
}