Developer Documentation

Integrate Netraksha AI APIs to detect deepfakes, fake profiles, and phishing links.

Overview

Welcome to the Netraksha AI developer documentation. Our platform provides a suite of cutting-edge AI endpoints designed to safeguard digital identities and prevent fraud. Whether you are building an enterprise security application or enhancing a consumer product, our APIs offer robust capabilities to seamlessly analyze media and URLs.

Quick Start: You will need an active API key to make requests. Head over to your dashboard to generate one.

Authentication

The Netraksha API uses API keys to authenticate requests. You can view and manage your API keys in the Netraksha Dashboard.

Authentication to the API is performed via the HTTP Authorization header. Provide your API key as a bearer token.

Authorization: Bearer sk_live_YOUR_API_KEY

Note: Use sk_test_ keys for development environments without incurring charges.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

API Endpoints

Identity Scan API

Scans the internet to detect if an image or username is being used in fake profiles or impersonation campaigns.

POST /api/scan
  • Input: image (multipart/form-data) or username (string)
  • Output: Overall risk score and an array of matched profiles across the web.

Deepfake Detection API

Analyzes an uploaded image or video to determine the probability that the media has been AI-generated or manipulated.

POST /api/deepfake-check
  • Input: media (file upload: image/video)
  • Output: Probability score indicating the likelihood of synthetic generation.

Link Scanner API

Evaluates a URL against our threat intelligence database and live behavioral models to detect phishing attempts and malicious redirects.

POST /api/link-check
  • Input: url (string)
  • Output: Status indicator (safe, phishing, or suspicious) with detailed reasoning.

Request & Response Examples

Netraksha AI APIs accept standard JSON payloads (unless file uploads are required, which use multipart/form-data) and return JSON-encoded responses.

Example: Link Scanner API Request

curl -X POST https://api.netraksha.com/v1/link-scan \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target_url": "https://suspicious-login.com"}'

Example: Link Scanner API Response

{
  "request_id": "req_8x99a2bC",
  "status": "success",
  "processing_time_ms": 142,
  "data": {
    "url": "https://suspicious-login.com",
    "verdict": "PHISHING",
    "risk_score": 98.5,
    "threat_indicators": [
      "Brand impersonation detected (LinkedIn)",
      "Domain registered less than 24 hours ago",
      "Zero-width characters hidden in URL"
    ]
  }
}

Rate Limits

API requests are subject to rate limiting based on your subscription tier to ensure platform stability and fairness.

Plan Tier Monthly Volume Rate Limit
Developer 10,000 req/mo 100 req/min
Production 100,000 req/mo 500 req/min
Enterprise Custom Volume Unlimited Concurrency

If you exceed the rate limit, the API will return a 429 Too Many Requests status code.

Error Codes

The Netraksha API uses standard HTTP response codes to indicate the success or failure of an API request.

Code Title Description
200 OK Everything worked as expected.
400 Bad Request The request was unacceptable, often due to missing a required parameter.
401 Unauthorized No valid API key provided.
429 Too Many Requests You hit the rate limit for your tier.
500 Internal Server Error Something went wrong on our end.