Skip to main content
This feature is currently in beta and is not fully rolled out to all customers. Features and functionality are subject to change. To request access to this feature, contact your Rhombus representative or post in the Rhombus Developer Community.

Overview

QR Code Unlock allows authorized users to gain entry by presenting a QR code to a Rhombus security camera or DR40 door controller. The camera recognizes the code, validates it against the Rhombus backend, and unlocks the door instantly when authorized. This implementation provides a fast, secure, and camera-authenticated method for controlled entry without requiring physical keycards, badges, or mobile apps.

How It Works

Use Cases

QR Code Unlock is ideal for various access control scenarios:

Office Visitors

Grant one-day or time-limited access to visitors without needing to issue physical badges.

Field Operations

Dispatch QR codes to technicians or contractors for temporary access to specific areas.

Multi-Tenant Buildings

Issue tenant-specific codes with customized durations for different access levels.

Deliveries & Access Windows

Schedule access during specific delivery hours with time-limited QR codes.

Prerequisites

Before implementing QR Code access control, ensure you have:
  • An active Rhombus account with API access
  • A valid API key from the Rhombus Console
  • At least one Rhombus camera or DR40 door controller configured for access control
  • The UUID of the access-controlled door you want to manage
You can find door UUIDs by listing all access-controlled doors in your organization using the POST /api/component/findAccessControlledDoors endpoint in the API Reference.

Generate a QR Access Code

Use the generateQRAccessCode endpoint to create a time-bound QR code for door access.

API Request

Request Parameters

string
required
The unique identifier of the door you want to authorize access to. This UUID can be obtained from the findAccessControlledDoors endpoint.
integer
required
Time in seconds the QR code will remain valid. Common values:
  • 3600 - 1 hour
  • 28800 - 8 hours (work day)
  • 86400 - 24 hours
  • 604800 - 7 days
string
Optional label identifying who the QR code was issued to (for example, the visitor’s name). Rhombus records this value on the resulting access audit events so unlocks can be attributed to the correct person.

Response

The API returns a JSON payload containing the QR code data as a base64-encoded string:
string
The QR code as a PNG image, returned as a base64-encoded byte array. Decode this to display or distribute the QR code.
string
The UUID of the generated access token backing this QR code. Use it to track or reference the issued credential.

Implementation Examples

Convert QR Code to Image

After receiving the base64 QR code from the API, you’ll need to convert it to a displayable image format.

Email QR Code to Visitor

Here’s a complete example of generating a QR code and emailing it to a visitor:
Python

Integration with Event Management System

Generate QR codes for event attendees:
Python

Security Considerations

Always protect your QR codes and implement appropriate security measures:

Time-Limited Access

  • Set appropriate validDurationSec values based on your use case
  • Shorter durations (1-8 hours) for visitor access
  • Longer durations (1-7 days) for contractor or temporary employee access
  • Never set unlimited duration codes

QR Code Distribution

Use secure email systems and verify recipient addresses before sending QR codes. Consider using encrypted email for sensitive access.
Verify phone numbers and use secure SMS services. Be aware that SMS may not be encrypted end-to-end.
Integrate QR code generation into your mobile app with proper authentication and user verification.
For printed codes, ensure physical security and proper disposal after expiration. Consider adding watermarks or other anti-copying measures.

Access Monitoring

  • Review access logs regularly using the Rhombus Console
  • Set up alerts for unusual access patterns
  • Monitor failed access attempts
  • Maintain audit trails of QR code generation and usage

Best Practices

Follow these best practices for a secure and efficient QR code access system:
  1. Validate Door UUIDs: Always verify door UUIDs before generating QR codes to ensure codes grant access to the correct doors.
  2. Implement Rate Limiting: If exposing QR code generation through your own application, implement rate limiting to prevent abuse.
  3. Log Generation Events: Keep records of who generated QR codes, for which doors, and with what validity periods.
  4. User-Friendly Expiration Times: When displaying QR codes, show the expiration time in the user’s local timezone.
  5. Test Before Distribution: Generate and test QR codes before sending to users to ensure they work correctly.
  6. Provide Instructions: Include clear instructions with QR codes on where to present them and what to expect.
  7. Error Handling: Implement proper error handling for API failures and invalid responses.

Benefits

QR code access provides touchless entry, works on any smartphone, and integrates with existing Rhombus access control hardware.

Troubleshooting

Common causes:
  • QR code has expired (it is valid for validDurationSec from the time it was generated)
  • Incorrect door UUID was used when generating the code
  • Camera is not properly configured for access control
  • QR code image is damaged or unclear
Solutions:
  • Generate a new QR code with a valid duration
  • Verify the door UUID using the findAccessControlledDoors endpoint
  • Check camera configuration in Rhombus Console
  • Ensure QR code is displayed clearly and at appropriate size
Common causes:
  • Invalid API key or authentication headers
  • Incorrect door UUID
  • Door not configured for QR code access
  • Insufficient permissions
Solutions:
  • Verify your API key in the Rhombus Console
  • Check that x-auth-scheme header is set to api-token
  • Confirm the door UUID exists and is configured for access control
  • Contact Rhombus support if the feature is not enabled for your account
Common causes:
  • Poor lighting conditions
  • QR code too small or too large
  • Camera angle is incorrect
  • QR code displayed on a reflective surface
Solutions:
  • Ensure adequate lighting at the entry point
  • Display QR code at 3-5 inches across
  • Position the QR code perpendicular to the camera
  • Avoid displaying on glossy screens—use matte screen protectors or print on paper

Next Steps

Webhook Integration

Set up webhooks to receive real-time access control events

Developer Community

Join the Rhombus Developer Community for support and updates

Rhombus Console

Manage your access control devices and settings
This feature is actively being developed. Stay tuned to the Rhombus Developer Community for updates on new functionality and improvements.
Last modified on July 8, 2026