Generate a vCard
API · /vcard-api
vCard API
Generate and parse vCard (.vcf) contact cards. Build a standards-compliant vCard 3.0 from simple fields — name (or first/last), organisation, job title, one or more phone numbers and emails, websites, a postal address, birthday, note and a photo URL — ready to download as a .vcf or embed in a contact QR code (pair it with the QR API for "scan to save contact"). Or go the other way: parse any vCard string back into clean structured fields. Pure local processing — no key, no third-party service, nothing stored. Live. 3 endpoints. Built for digital business cards, contact QR codes, address-book import/export, CRM integrations and email-signature tools.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 86 ms
- Server probes · 24h
- Subscribers
- 3,680
- active
- Total calls
- 42
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,600 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,600 calls/month
- 2 req/sec
- Generate + parse
- No credit card
Starter
€7.80 /month
- 33,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 33k calls/month
- 8 req/sec
- Multi phone/email/url
- Email support
Pro
€27.40 /month
- 192,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 192k calls/month
- 20 req/sec
- CRM / signature tools
- Priority support
Mega
€63.40 /month
- 980,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 980k calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
QR Code with Logo API
Generate branded QR codes with a centre logo overlay, custom foreground and background colors, chosen size and error-correction level, as PNG or SVG. When a logo is supplied the error-correction level is raised automatically so the code stays scannable, and the logo is placed on a rounded white plate in the centre. Includes one-call helpers that build the correct payload for you: a Wi-Fi-join QR (SSID, password, encryption, hidden), a vCard contact QR (name, phone, email, organisation, title, URL, address) and a batch endpoint that returns up to 100 QR codes in a single request. Supply a logo by public URL, base64 or a raw binary body; receive results as base64 PNG/SVG JSON or, with raw=1, the raw image bytes. Pure server-side rendering (qrcode + sharp), no third-party upstream. Ideal for marketing and packaging, business cards and events, restaurant menus, Wi-Fi sharing and app onboarding.
api.oanor.com/qrlogo-api
Blackjack Strategy API
Blackjack maths as an API, computed locally and deterministically and exactly — the hand value, the textbook basic-strategy play and the dealer odds, the numbers that hold the house edge to half a percent. The hand-value endpoint scores a hand the way the table does: aces count 11 unless that busts, then 1, so it reports the best total, whether it is soft (an ace still counting 11, safe to hit) or hard, whether it busts, and whether two cards make a blackjack. The strategy endpoint gives the correct basic-strategy action — hit, stand, double or split — for any hand against the dealer's upcard, for the standard 4-to-8-deck game where the dealer stands on soft 17 with double-after-split allowed: 16 against a 10 hits, a pair of 8s always splits, soft 18 doubles against a 6 but hits against a 9, and 11 doubles against everything but an ace. The dealer-odds endpoint gives the dealer's bust probability by upcard — a 5 or 6 busts about 42 % of the time, an ace only 12 % — the reason you stand on stiffs against weak upcards. Everything is computed locally and deterministically, so it is instant and exact. Ideal for blackjack trainers and strategy apps, card-game and casino-game tools, learning aids, and game back-ends. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — not betting advice; the house always keeps an edge.
api.oanor.com/blackjack-api
Steel Heat-Treat API
Steel heat-treatment maths as an API, computed locally and deterministically — the temperatures and hardness numbers a bladesmith, machinist or metallurgist works to. The critical-temp endpoint gives the critical and process temperatures from carbon content: the lower critical A1 is 727 °C and the upper critical A3 ≈ 910 − 203·√(%C), so a 0.4 %-carbon steel has an A3 around 782 °C and hardens about 817 °C (austenitize 30–50 °C above A3, then quench), while a hypereutectoid steel austenitizes just above A1. The tempering endpoint maps temper oxide colours to temperature both ways — light straw at about 204 °C for hard cutting edges, purple around 282, blue around 304 for springs — with the typical use at each, the colour you watch on bright steel as you draw the hardness back. The hardness endpoint converts between Rockwell C, Brinell and tensile strength (SAE J417 / ASTM E140): HRC 50 is roughly 481 Brinell and about 1,660 MPa tensile, since tensile ≈ 3.45 × Brinell. Everything is computed locally and deterministically, so it is instant and private. Ideal for bladesmithing and metalworking apps, machine-shop and heat-treat tools, materials-engineering calculators, and trade study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Plain-carbon-steel estimates — alloy steels and a tested chart differ.
api.oanor.com/heattreat-api
Industrial Coatings API
Industrial and protective-coatings maths as an API, computed locally and deterministically — the film-build numbers a coatings inspector, painter or estimator works to, the ones simple paint estimating skips. The coverage endpoint gives theoretical and practical coverage from the coating's volume solids and the target dry film thickness: coverage = 1604 × the volume-solids fraction ÷ the DFT in mils, where 1604 is the square feet a gallon covers at one mil — so a 50 %-solids coating at 2 mils dry covers about 401 ft² per gallon, less a loss factor for overspray and surface profile. The film-thickness endpoint converts between wet and dry film thickness through the volume solids: WFT = DFT ÷ the solids fraction, because the solvent flashes off and the film shrinks, so a 50 %-solids coating laid 4 mils wet dries to 2 mils — the number you check with a wet-film comb as you spray. The transfer-efficiency endpoint gives the real material needed: theoretical gallons ÷ the transfer efficiency, since conventional spray lands only ~25 % on the part, HVLP ~65 %, electrostatic up to ~95 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for coatings-estimating and inspection apps, industrial-painting and protective-coating tools, NACE/SSPC study aids, and spec calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For simple wall-paint area estimating use a paint API.
api.oanor.com/coating-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for vCard API?
What's the rate limit for vCard API?
How much does vCard API cost?
Can I cancel my subscription anytime?
Is vCard API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/vcard-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/vcard-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/vcard-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/vcard-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 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.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.