Programmatic access to the TraceFind investigation engine. Search emails,
usernames, and phone numbers across hundreds of sources. Stream results
in real time, generate reports, and manage credits — all from a single,
consistent API surface.
Base URLhttps://tracefind.info
ProtocolHTTPS · JSON · SSE
AuthenticationBearer Token
Cost per search5 credits
01 — Getting Started
Overview
The TraceFind API is a JSON-over-HTTPS service. Most endpoints are protected by a Bearer token tied
to a user account; the email reconnaissance endpoint streams results over Server-Sent Events.
Costly searches consume credits — typically 5 credits per query, automatically refunded if no findings are returned.
Base URL
https://tracefind.info
Default content type
application/json
01 — Getting Started
Authentication
Most endpoints expect a Bearer token in the Authorization header.
The token is your user_id, returned by /signup.
Errors return standard HTTP status codes with a JSON { "detail": "..." } body.
Header
HTTP
Authorization: Bearer YOUR_TOKEN
Note
Credit policy. Each authenticated search costs 5 credits. If a search returns no findings, credits are refunded automatically. Insufficient balance returns 400 Too low on credits.
02 — Account
Account
Create accounts, sign in with an existing account number, and check the remaining credit balance.
POST/signupPublic
Provisions a new user account. Returns a 12-character user_id that doubles as your authentication token. Store it safely — there is no password recovery.
Request
cURL
curl -X POST https://tracefind.info/signup
200 OK
JSON
{
"msg": "Success",
"user_id": "YOUR_TOKEN"
}
POST/loginPublic
Verifies an existing account by its account_number (the user_id returned from signup). Returns the same id on success.
The investigative core of the API. Email searches stream live as services are queried; username and phone searches return their full result set in one response. Each search costs 5 credits.
GET/stream/{email}Auth required
Streams an OSINT search across hundreds of services for the given email address using Server-Sent Events. Each event is a JSON payload describing one finding (social account, leak, Google profile data, etc.). The stream terminates with a literal [STOP] marker and a final report_id used to retrieve the PDF later.
Auth note. Because EventSource can't set headers, this endpoint accepts the auth token via the auth_token query parameter instead of a Bearer header.