Build with Signal SearchProduction ready API reference, shared subscription limits, structured JSON responses
API v1.3Getting started
Create an API key in Settings and than Developer API. Send HTTPS POST requests with JSON, and your API key in the X-API-Key header. The sample fields below match each module’s actual request parser.
Store API keys server-side only. Do not share keys in screenshots or frontend code. Developer access, IP whitelisting, plan quotas and restrictions apply.
Authentication
curl -X POST "https://www.signalsearch.net/api/lookupclient/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"123456789112345678"}'On Windows CMD use a single-line command with escaped JSON quotes or use PowerShell. The backslash form above is for bash/zsh.
Shared Plan Search Limits
Your API key is an access method, not a second plan. All successful searches made through the API and dashboard count toward the same daily search allowance for the key owner's Basic, Starter or Pro plan. There is no separate API hourly quota or IntelX daily quota.
Plan-specific module restrictions continue to apply. Reaching the shared daily allowance returns HTTP 429. Search usage resets at the database server's midnight (the same boundary as the dashboard).
Status and rejected/invalid requests are recorded in the API audit log, but do not consume searches. API request counts are informational, not a separate request limit. Successful searches from either interface use the same search_logs ledger.
Key Status
Check your key, shared plan search usage, remaining daily searches, last usage timestamp and plan expiry. No JSON body needed.
curl -X POST "https://www.signalsearch.net/api/status" \
-H "X-API-Key: YOUR_API_KEY"
Example response (illustrative values)
{
"status": "active",
"service": "signalsearch.net",
"tier": "starter",
"usage": {
"total_requests": 153,
"total_searches": 412,
"daily_searches": 12,
"daily_limit": 100,
"remaining_today": 88,
"search_limit_resets_at": "2026-11-18 00:00:00"
},
"account": {
"key_prefix": "ss_Example",
"last_used": "2026-11-17 12:00:00",
"expiry": "2026-12-01 00:00:00"
},
"endpoints": {"documentation": "https://www.signalsearch.net/api/docs"},
"timestamp": "2026-11-17T12:00:00Z"
}Errors
{"ok":false,"error":"Daily search limit reached","message":"Retry when your plan search allowance resets.","service":"Signal Search API"}Lookup Client
POST /api/lookupclient/searchSearch indexed records and approved external sources
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/lookupclient/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"123456789112345678"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
IntelX
POST /api/intelx/searchRetrieve IntelX content using its Storage ID, with optional automatic bucket discovery. This is the same Storage ID workflow used in the Signal Search dashboard; no separate fetch endpoint is required.
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/intelx/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"storageid":"YOUR_STORAGE_ID"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The response includes the IntelX content in result.preview_text, along with the resolved bucket and additional metadata.
Crypto Analyzer
POST /api/cryptoanalyzer/searchAnalyze a crypto wallet
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/cryptoanalyzer/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
IP Resolver
POST /api/ipresolver/searchNetwork and geolocation details
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/ipresolver/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ip":"8.8.8.8"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
Discord Resolver
POST /api/discordresolver/searchResolve a Discord identifier
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/discordresolver/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"discord_id":"123456789012345678"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
Steam Resolver
POST /api/steamresolver/searchSteam metadata
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/steamresolver/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"steam":"11000010abcdef0"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
Xbox Resolver
POST /api/xboxresolver/searchXbox profile lookup
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/xboxresolver/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"xbox":"ExampleGamer"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
CFX Resolver
POST /api/cfxresolver/searchCFX identifier or server search
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/cfxresolver/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"cfx":"example"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.
CFX Player Database
POST /api/cfxplayerdatabase/searchSearch player records by a supported identifier, using the same CFX Player Database backend as the dashboard. Use only for identifiers you are authorized to investigate.
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/cfxplayerdatabase/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"discord_id","value":"123456789012345678"}'Example response
{
"ok": true,
"result": {
"query": "123456789012345678",
"search_type": "discord_id",
"total": 0,
"profiles_attempted": 0,
"players": [],
"cached": false
}
}Results follow the existing dashboard parser. Returned fields depend on the linked records and provider response. Validation errors return 422; upstream availability errors return 502 or 503. Plan and API rate limits apply.
AI Geolocation
POST /api/aigeolocation/searchEstimate location from supplied image
Parameters
Example request
curl -X POST "https://www.signalsearch.net/api/aigeolocation/search" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"image":"BASE64_ENCODED_IMAGE"}'Response format
{
"ok": true,
"result": {
"...": "module-specific fields"
}
}The returned result contains the existing module-specific fields. The response uses the existing module response schema.