Developer docs

Auth Docs and API Access

Public discovery endpoints, OpenAPI metadata, MCP discovery, and vCard payload generation do not require authentication.

Public Endpoints

No API key required: GET /v1/health, GET /v1/product, POST /v1/vcard, GET /mcp, and POST /mcp.
CORS: Public API responses allow browser-based agents and automation clients to read the endpoints.
Privacy: The free static generator runs QR rendering in the browser. The API returns vCard text for user-authorized workflows; it does not create accounts or store contacts.

Authenticated Product Areas

Dynamic QR profiles, analytics dashboards, billing, and user-owned edits live at app.vcardqrcodegenerator.com. Agents should not modify user-owned dynamic QR resources unless an authenticated app flow is explicitly documented and authorized by the user.

Agent Auth Walkthrough

Call GET https://vcardqrcodegenerator.com/api/v1/health to verify the public API is reachable.
Call GET https://vcardqrcodegenerator.com/api/v1/templates to choose a vCard QR template.
Call POST https://vcardqrcodegenerator.com/api/v1/vcard with sample contact fields and optional Idempotency-Key.
Parse structured JSON errors using error.code, error.message, error.hint, error.docsUrl, and error.status.

OAuth metadata is intentionally not required for these public sandbox-style endpoints. User-owned dynamic QR actions remain app-authenticated and should not be automated until a user explicitly authorizes that flow.