Every document task,
one API
Production-grade, versioned endpoints with predictable pricing, typed SDKs, and 99.99% uptime. Authenticate once — call anything.
One platform, every document task
Pick an endpoint and start calling it in minutes — every API shares the same auth, conventions, and SDKs.
How the API Key and Link Actually Work
Everything you need to know after generating your API key: link structure, bearer headers, payloads, and live examples.
1. Your Secret API Key
Generated in your Developer Account. It begins with vrn_ and acts as your secret credential. The server never stores the raw key—only an encrypted SHA-256 hash.
2. The Endpoint Link
Every Veron service has a dedicated HTTPS endpoint link (e.g. https://api.veron.io/v1/qr or /v1/pdf/to-word). All links are versioned under /v1/ for long-term stability.
3. Authorization Header
Pass your key in the standard HTTP header: Authorization: Bearer <YOUR_API_KEY>. The server authenticates your identity before executing any document or AI pipeline.
Making Your First Call
See how the link and key assemble into a working request in your preferred language.
Use the base link /v1 followed by the service path (e.g. /v1/qr, /v1/pdf/compress).
Always set Authorization: Bearer <key>. Unauthenticated requests are rejected with 401.
JSON tools return typed JSON or images. PDF/Image tools return downloadable binary attachments directly.
Veron v1 Endpoint Directory
Scale you can rely on
Ship your first API call
in under a minute
Grab a key, paste a snippet, and you're live. 10,000 requests free every month.