DeepfakeDetector.ai API: Image & Video Verification Guide
Learn how to integrate the DeepfakeDetector.ai API to detect synthetic media, handle image and video scans, and manage webhooks securely.

Stock photo for illustration only, not from the actual event
- Integrate DeepfakeDetector.ai API for robust image and video verification
- Supports major AI generators including Midjourney, DALL-E, Stable Diffusion, and Flux
- Step-by-step implementation for URL and multipart form data requests
- Utilize webhooks and job IDs efficiently for asynchronous long video processing
If your platform accepts user-uploaded images or videos, synthetic media is already infiltrating your pipeline. Profile photos, onboarding selfies, and user-generated content clips submitted to newsrooms all contain a growing fraction of generated or manipulated material that requires active moderation.
This guide covers adding detection using the DeepfakeDetector.ai API: acquiring an API key, scanning images, handling asynchronous video processing, defensively parsing responses, and designing your product around probabilities rather than absolute facts. All endpoints reside behind a single base URL at https://app.deepfakedetector.ai/api/v1.
For images, the API targets AI-generated visuals and faces from major generators like Midjourney, DALL·E, Stable Diffusion, and Flux. For videos, it covers face swaps, lip-sync manipulation, and fully AI-generated clips analyzed frame by frame. API access begins on the Starter plan, while the free tier provides 50 monthly detections via the web app for evaluation purposes.
Once you subscribe to a plan with API access, your secret key is displayed only once. You must copy it immediately into your secrets manager and keep it strictly server-side. Requests require a Bearer token, and exposing a key within a browser bundle poses severe security risks.
Your first image request can be made by sending a publicly reachable HTTPS URL to the detect/image endpoint. Optional parameters allow the use of short-lived signed URLs for private storage files. Alternatively, if you possess the file locally, you can submit it as multipart form data supporting MP4, MOV, WEBM for video, and JPG, PNG, WEBP for images.

Stock photo for illustration only, not from the actual event
Contextual Analysis: A critical operational practice is scanning the user-submitted file before transcoding, resizing, or compressing it for storage. Re-encoding degrades the microscopic artifacts relied upon by detectors, and heavy compression is frequently cited as the primary reason behind inconclusive scan results.
For video files exceeding 60 seconds, utilizing a webhook is essential. By passing a callback_url parameter, the API transmits the verdict back upon analysis completion, sparing you from maintaining an open HTTP request for the duration of the video rendering process.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment