QR-V™ API • QRVP-1 Protocol
QR-V™ API Documentation
The QR-V™ API provides programmatic access to verification and issuance workflows within the QR-V Global Verification Network.
—
Base Endpoint
https://api.qrv.network/v1/
—
Authentication
The QR-V™ API uses API key-based authentication.
Authorization: Bearer YOUR_API_KEY
API keys are issued through the QR-V issuer platform or enterprise onboarding process.
—
Verification Endpoint
GET /verify/{qrv_id}
Resolves a QR-V identifier and returns verification data.
Example Request
GET https://api.qrv.network/v1/verify/QRV-123456789
Example Response
{
"status": "verified",
"issuer": "Example Authority",
"type": "certificate",
"timestamp": "2026-03-19T14:00:00Z",
"record_id": "QRV-123456789"
}
—
Issuance Endpoint
POST /records
Creates a new verification record and binds a QR-V identifier.
Example Request
POST https://api.qrv.network/v1/records
{
"type": "certificate",
"issuer": "Example Authority",
"metadata": {
"name": "John Doe",
"course": "Security Training"
}
}
Example Response
{
"status": "created",
"qrv_id": "QRV-123456789"
}
—
Record Status
Verification responses may return the following statuses:
- verified — record is valid
- revoked — record has been invalidated
- expired — record is no longer valid
- not_found — no matching record exists
—
Error Handling
{
"error": "invalid_request",
"message": "Missing or malformed QR-V identifier"
}
—
Rate Limits
- Standard: 100 requests / minute
- Enterprise: Custom limits available
—
Security Model
- Registry-backed verification (source of truth)
- No client-side validation assumptions
- Deterministic API responses
- Separation of identifier and record data
- Support for revocation and lifecycle changes
—
Integration Flow
Create Record → Generate QR-V → Distribute → Scan → Verify via API → Return Result
—
Get API Access
Request API credentials and begin integrating QR-V verification into your systems.
—
QR-V™ API • QRVP-1 • Registry-Based Verification Infrastructure