Fintech
Identity Verification Pipelines
KYC and onboarding services call the API from their verification workflow to confirm that the photo on a submitted ID matches the person elsewhere on the public web.
FaceSearch REST API
Run Face Searches From Any Language
The FaceSearch REST API gives developers a small, stable surface for reverse face image search: submit a photo, poll for completion, read results. Bearer-token auth, idempotent retries, and a public OpenAPI spec.
One endpoint • 3 credits per search • JSON everywhere
Trusted by thousands worldwide
15,000+ Searches
50+ Countries
256-bit Encryption
99.7% Accuracy
How the REST API Works
Three steps from a blank terminal to your first search result.
1
Create an API Key
Log in to the dashboard and generate a key. The plaintext is shown exactly once. Store it in your secrets manager and never commit it to source.
2
POST Your Image
curl -F [email protected] https://facesearch.net/api/v1/search with your Bearer header. The endpoint returns a jobId in under a second.
3
Poll Until Completion
GET /api/v1/search/{jobId} every 3-5 seconds. When status is completed, the response includes matched source URLs, thumbnails, and confidence scores.
REST API Features
Everything you need to integrate face search into a production backend.
REST API Features
Everything you need to integrate face search into a production backend.
OpenAPI 3.1 Spec
Hand-written OpenAPI document at /api/v1/openapi.json powers every type-safe SDK, from Postman imports to generated clients in 20+ languages.
Idempotent Retries
Send an RFC 9110 Idempotency-Key header and the server returns the same jobId for duplicate submits. Omit it and the server derives a content hash automatically, so naive retries are always safe.
Per-Key Quotas
Each API key can carry an optional daily and monthly cap. A leaked key cannot drain your whole balance because the quota is enforced at Redis speed with a Postgres fallback.
Granular Rate Limits
Every response carries X-RateLimit-Remaining and X-RateLimit-Reset headers. 429 responses include Retry-After so you know exactly when to try again.
Shared Credit Pool
API usage draws from the same credit balance as the web UI. One top-up in the dashboard powers both surfaces with no new billing SKU to manage.
Predictable Errors
Every error response is a stable envelope: code, message, status. Codes like INSUFFICIENT_CREDITS and RATE_LIMITED never change, so your error handling can be boring and forever.
Copy. Paste. Ship.
Every FaceSearch API call is one HTTP request. Here is the same 'submit a face search' flow in five languages.
Terminal one-liner
# 1. Submit a face image for search
curl -X POST https://facesearch.net/api/v1/search \
-H "Authorization: Bearer fs_live_YOUR_KEY" \
-H "Idempotency-Key: submit-$(date +%s)" \
-F "image=@/path/to/face.jpg" \
-F "consent=true"
# 2. Poll for completion
curl https://facesearch.net/api/v1/search/JOB_ID \
-H "Authorization: Bearer fs_live_YOUR_KEY"
# 3. Check your credit balance
curl https://facesearch.net/api/v1/credits \
-H "Authorization: Bearer fs_live_YOUR_KEY"Who Builds on the REST API
From background checks to safety tooling, the API powers teams that need face search at scale.
Safety
Automated Moderation
Trust and safety teams wire the API into their incident response pipeline so escalated user reports can be enriched with context in seconds, not hours.
Research
Investigative Research
Investigative journalists and OSINT researchers script bulk face searches from Jupyter notebooks, using the idempotency key header to deduplicate overnight batch runs.
Trusted Face Search Platform
10M+
Searches Completed
Trustworthy results worldwide
95%
Match Accuracy
Powered by advanced AI
50K+
Active Users
Growing community
100M+
Sources Scanned
Comprehensive coverage
What Developers Say About the API
Real feedback from teams integrating FaceSearch into production workflows.
"The hybrid idempotency key policy is the best I've seen on any API. Naive retries just work, and explicit keys give us full control when we need fresh searches."
"We wired FaceSearch into our moderation pipeline in an afternoon. The per-key quotas let us hand different teams their own keys without worrying about someone accidentally draining the pool."
"The OpenAPI spec let me generate a typed Python client in one command. Error codes never change, so my pipeline has been boring in the best way for months."
Simple, Transparent Pricing
Choose the plan that fits your needs. No hidden fees, cancel anytime.
MOST POPULAR
PRO
$29/month
For professionals and power users
- 100 Credits per month ($0.29 per credit)
- Face Search
- Search History
- Can Export Profile to PDF
Pay As You Go
Or Buy Credit Packs
Starter
3credits
$6
$2.00/credit
SAVE 20%
Basic
30credits
$24
$0.80/credit
SAVE 31%
Standard
100credits
$69
$0.69/credit
SAVE 34%
Pro
300credits
$199
$0.66/credit
SAVE 40%
Enterprise
1000credits
$599
$0.60/credit
REST API FAQ
Everything developers ask before writing their first request.
Start Building With the REST API
Create a free API key, paste the curl one-liner, and run your first search in under ten minutes.
Create an API Key
No credit card required
