NSFW Image DetectorNSFW Image Detector API

OnlineCredit Usage:10 per callRefreshed 1 month ago
avg: 3147ms|p50: 2769ms|p75: 3399ms|p90: 4154ms|p99: 5665ms

NSFW Detector is a simple tool for detecting NSFW content. It returns a boolean

The NSFW Image Detector API provides reliable and fast access to nsfw image detector data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use NSFW Image Detector, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/nsfwimagedetector

Code Examples

Here are examples of how to call the NSFW Image Detector API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/nsfwimagedetector" \
  -H "X-API-Key: your_api_key_here" \
  -F "image=@/path/to/image.jpg"
JavaScript (Fetch API)
const formData = new FormData();
formData.append('image', fileInput.files[0]);

const response = await fetch('https://api.apiverve.com/v1/nsfwimagedetector', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here'
  },
  body: formData
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here'
}

files = {
    'image': open('/path/to/image.jpg', 'rb')
}

response = requests.post('https://api.apiverve.com/v1/nsfwimagedetector', headers=headers, files=files)

data = response.json()
print(data)
Node.js (Native HTTPS)
const fs = require('fs');
const FormData = require('form-data');

const form = new FormData();
form.append('image', fs.createReadStream('/path/to/image.jpg'));

fetch('https://api.apiverve.com/v1/nsfwimagedetector', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    ...form.getHeaders()
  },
  body: form
})
.then(res => res.json())
.then(data => console.log(data));
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/nsfwimagedetector');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here'
]);

$postFields = [
    'image' => new CURLFile('/path/to/image.jpg')
];

curl_setopt($ch, CURLOPT_POSTFIELDS, $postFields);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

import (
    "bytes"
    "fmt"
    "io"
    "mime/multipart"
    "net/http"
    "os"
)

func main() {
    file, _ := os.Open("/path/to/image.jpg")
    defer file.Close()

    body := &bytes.Buffer{}
    writer := multipart.NewWriter(body)
    part, _ := writer.CreateFormFile("image", "image.jpg")
    io.Copy(part, file)
    writer.Close()

    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/nsfwimagedetector", body)
    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", writer.FormDataContentType())

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    respBody, _ := io.ReadAll(resp.Body)
    fmt.Println(string(respBody))
}
Ruby (Net::HTTP)
require 'net/http'
require 'uri'
require 'json'

uri = URI('https://api.apiverve.com/v1/nsfwimagedetector')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Post::Multipart.new(
  uri.path,
  'image' => UploadIO.new(File.open('/path/to/image.jpg'), 'image/jpeg', 'image.jpg')
)

request['X-API-Key'] = 'your_api_key_here'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.IO;
using System.Net.Http;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        using var content = new MultipartFormDataContent();
        using var fileStream = File.OpenRead("/path/to/image.jpg");
        content.Add(new StreamContent(fileStream), "image", "image.jpg");

        var response = await client.PostAsync("https://api.apiverve.com/v1/nsfwimagedetector", content);
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The NSFW Image Detector API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the NSFW Image Detector API directly in your browser with live requests and responses.

File Upload Required

The NSFW Image Detector API requires file upload via multipart/form-data. Do not use Content-Type: application/json for NSFW Image Detector.
PropertyValue
Field Nameimage
Accepted Types.jpg, .jpeg, .png, .gif
Max File Size10MB
File Upload Example (cURL)
curl -X POST "https://api.apiverve.com/v1/nsfwimagedetector" \
  -H "X-API-Key: your_api_key_here" \
  -F "image=@/path/to/your/file"
File Upload Example (JavaScript)
const formData = new FormData();
formData.append('image', fileInput.files[0]);

const response = await fetch('https://api.apiverve.com/v1/nsfwimagedetector', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here'
  },
  body: formData
});

const data = await response.json();
console.log(data);

Parameters

The following parameters are available for the NSFW Image Detector API:

Detect NSFW

ParameterTypeRequiredDescriptionDefaultExample
imagestringoptional
Upload an image file containing the image needing classification (supported formats: JPG, PNG, GIF)
-https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Camponotus_flavomarginatus_ant.jpg/640px-Camponotus_flavomarginatus_ant.jpg

Response

The NSFW Image Detector API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "isNSFW": false,
    "isSafe": true,
    "confidence": 0.987,
    "category": "neutral"
  }
}
XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <isNSFW>false</isNSFW>
    <isSafe>true</isSafe>
    <confidence>0.987</confidence>
    <category>neutral</category>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  isNSFW: false
  isSafe: true
  confidence: 0.987
  category: neutral
CSV Response
200 OK
keyvalue
isNSFWfalse
isSafetrue
confidence0.987
categoryneutral

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
isNSFWbooleanfalseWhether the image contains NSFW content
isSafebooleantrueWhether the image is safe for general audiences
confidencePremiumnumber0.987Confidence score from 0 to 1 for classification accuracy
categoryPremiumstring"neutral"Content classification category (neutral, suggestive, NSFW)

Headers

Required and optional headers for NSFW Image Detector API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about request headers →

CORS Support

The NSFW Image Detector API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call NSFW Image Detector directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call NSFW Image Detector directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

NSFW Image Detector API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all NSFW Image Detector users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each NSFW Image Detector response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, NSFW Image Detector returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for NSFW Image Detector:

  • Monitor the rate limit headers to track your NSFW Image Detector usage (Free plan only)
  • Cache nsfw image detector responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle NSFW Image Detector performance

Note: NSFW Image Detector rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using NSFW Image Detector on Free tier.

Error Codes

The NSFW Image Detector API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate NSFW Image Detector with SDKs

Get started quickly with official NSFW Image Detector SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate NSFW Image Detector with No-Code API Tools

Connect the NSFW Image Detector API to your favorite automation platform without writing code. Build workflows that leverage nsfw image detector data across thousands of apps.

All platforms use your same API key to access NSFW Image Detector. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for NSFW Image Detector?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for NSFW Image Detector and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does NSFW Image Detector cost?

Each successful NSFW Image Detector API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful nsfw image detector lookups.

Can I use NSFW Image Detector in production?

The free plan is for testing and development only. For production use of NSFW Image Detector, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use NSFW Image Detector from a browser?
Yes! The NSFW Image Detector API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my NSFW Image Detector credit limit?

When you reach your monthly credit limit, NSFW Image Detector API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?