API · /filetype-api

File Type Detection API

healthy 4,540 Subscribers

Detect the true type of a file from its content — its magic bytes / binary signature — not from its name. Send a file by URL or base64 and get back the real extension and MIME type, recognising 100+ binary formats: images (PNG, JPEG, GIF, WebP, AVIF, HEIC), audio and video (MP3, MP4, WAV, FLAC, MKV), archives (ZIP, GZIP, 7z, RAR, TAR), documents (PDF, DOCX, XLSX), fonts and more. Optionally pass a filename to flag a spoofed extension (e.g. a PNG renamed to .txt). Text formats like TXT, CSV, JSON and SVG have no signature and return detected=false. Detection is local — no key, no third-party service. Live, nothing stored. 2 endpoints. Built for secure upload validation, anti-spoofing checks, content pipelines and forensics. Distinct from an extension-to-MIME lookup.

#file-type #magic-bytes #mime #security #developer-tools #upload

api.oanor.com/filetype-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/filetype-api/openapi.json

/api/filetype-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 91 ms; Server probes · 24h
Subscribers: 4,540; active
Total calls: 28; last 7 days

Full status page → · 10 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

1,320 calls / month
2 requests / second
Hard cap (429 above quota, no overage)
1,320 calls/month
2 req/sec
100+ formats, URL + base64
No credit card

Starter

€5.00 /month

19,000 calls / month
8 requests / second
Hard cap (429 above quota, no overage)
19k calls/month
8 req/sec
Spoofed-extension checks
Email support

Pro

€24.60 /month

164,000 calls / month
20 requests / second
Hard cap (429 above quota, no overage)
164k calls/month
20 req/sec
Upload-validation pipelines
Priority support

Mega

€60.60 /month

840,000 calls / month
50 requests / second
Hard cap (429 above quota, no overage)
840k calls/month
50 req/sec
Platform scale
Dedicated SLA

Built by

PremiumApi

Related APIs

Other APIs with overlapping tags.

MIME API

A fast, fully-local MIME and file-type toolkit: look up the MIME type, charset and category for a filename or extension, list every file extension registered for a MIME type, and detect a file's real type from its leading magic bytes (over 40 signatures, including RIFF container disambiguation for WEBP, WAV and AVI), accepting hex or base64 input. Every endpoint accepts input via the query string or the request body. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for upload validation, security (verify a file's real type against its claimed extension), CDNs and content pipelines.

api.oanor.com/mime-api

MIME Encoding API

The email and MIME text encodings that general base64/hex toolkits leave out. The quoted-printable endpoint encodes and decodes Quoted-Printable (RFC 2045) — the Content-Transfer-Encoding that keeps mostly-ASCII text readable while escaping everything else as =XX hex, with the soft line-wrapping at 76 columns and trailing-whitespace handling the spec requires. The encoded-word endpoint encodes and decodes RFC 2047 encoded-words — the =?UTF-8?Q?…?= and =?UTF-8?B?…?= form used to carry non-ASCII text in email Subject, From, To and other headers — in either the Q (quoted-printable-style) or B (base64) variant, and decodes any mix of them back to plain text. Everything is UTF-8 and computed locally and deterministically, so it is instant and private. Ideal for building and parsing email (SMTP/IMAP), .eml and MIME tooling, newsletter and transactional-mail systems, and migrating legacy mail data. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. These are the MIME-specific encodings; for base64, base32, hex, URL and HTML entity encoding use a general encoding API.

api.oanor.com/mimeencode-api

Email Parser API

Parse a raw email (RFC 822 / MIME / .eml) into clean, structured data. Send the raw message (or a URL to a .eml file) and get back the sender, recipients (to / cc / bcc / reply-to) with names and addresses split out, the subject, the parsed date, the Message-ID, In-Reply-To and References (for threading), priority, the plain-text and HTML bodies, every header, and metadata for each attachment (filename, content type, size, content-id — never the binary payload). A /v1/headers endpoint returns just the header map. Parsing is fully local (no third-party service) and nothing is stored. Live. 3 endpoints. Built for inbound-email processing, .eml viewers, mailbox import, ticketing and email-automation pipelines. Distinct from address validation and SPF/DMARC checks.

api.oanor.com/emailparse-api

Birthday Paradox API

Birthday-paradox and collision-probability maths as an API, computed locally and deterministically. The probability endpoint computes the chance that at least two of n people share a birthday among d equally likely days, P = 1 − Π(1 − i/d), evaluated in log space for accuracy — the famous result that just 23 people give about a 50.7 % chance, 50 people about 97 % and 70 people about 99.9 %. The people-needed endpoint inverts it: the smallest group size to reach a target probability (23 for 50 %, 57 for 99 %), with the √(2·d·ln(1/(1−p))) approximation. The collision endpoint generalises the birthday bound to any space — pass a number of buckets or a hash size in bits — and returns the collision probability P ≈ 1 − e^(−n²/2d), the rule behind hash collisions and UUID-uniqueness estimates, where a 50 % chance needs roughly 1.177·√d items. Days and buckets default to 365. Everything is computed locally and deterministically, so it is instant and private. Ideal for probability-education, security, cryptography, hashing, data-engineering and statistics app developers, collision-risk and birthday-problem tools, and teaching material. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the birthday/collision probability; for full distributions use a probability API.

api.oanor.com/birthdayparadox-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for File Type Detection API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call File Type Detection API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for File Type Detection API?

Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.

How much does File Type Detection API cost?

File Type Detection API has a free tier with 100 calls / month. Paid plans start at €5.00 / month with higher quotas and faster rate limits.

Can I cancel my subscription anytime?

Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.

Is File Type Detection API GDPR-compliant?

All requests to File Type Detection API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Detect 1

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/detect

Detect file type from content

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

curl https://api.oanor.com/filetype-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."

const res = await fetch("https://api.oanor.com/filetype-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();

$ch = curl_init("https://api.oanor.com/filetype-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);

import requests
r = requests.get(
    "https://api.oanor.com/filetype-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 This thread is locked — no new replies.

No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.