Access control
Prepare visitor records while your reception team focuses on the visit.
IdScanly extracts structured fields from supported identity documents for your visitor-management software. Use the results to prefill registration records, compare names with appointments and prepare approved details for your badge or access workflow.
Synthetic data. A possible integration, not a ready-made connector or a live product screen.
DEMO-0001DEMO-0100Reception teams often need to find an appointment, identify the host, record a visitor’s name and prepare a pass. Copying document details into several screens adds repetitive work when people arrive together or at busy times.
A visitor registration ID scanner API helps prepare the data entry portion of that process. Your application sends a document image to IdScanly, receives structured fields and presents a draft visitor record for review.
The visitor-management system remains responsible for the appointment, host, visit purpose and admission rules. OCR supplies document information that staff would otherwise need to transcribe.
Connect the visitor’s document session to the appointment. Your application can compare the extracted name with the invitation while reception confirms the host, location and time of the visit.
Show meaningful differences for review. The name on a booking may be abbreviated or entered in a different order from the name printed on the document.
Prepare a new draft record from the permitted document fields. Reception can add the host and purpose, then follow your site’s approval process before issuing access.
Maintain a separate person record for each visitor and connect them to the shared appointment or host. This keeps badge details and visit records associated with the correct individual.
Where your site requires document-based registration, use OCR to prepare the relevant identity fields. Link those fields to your own contractor record, appointment or work authorisation process without treating the scan as approval to enter.
The available output depends on the document and supported fields. A visitor workflow may use a name and document type, with selected identifiers or validity information only when required for the site’s process.
Keep document-derived information separate from visit information:
| Document information | Information supplied by your visitor system |
|---|---|
| Visitor name | Host or responsible contact |
| Document type | Appointment and visit purpose |
| Selected document reference, where needed | Site, building or reception location |
| Available validity details, where needed | Permitted visit period and approval status |
Your badge template can use the minimum approved information, such as a name and visit reference. It does not need to reproduce every field available from the document.
This workflow can be built into reception software, a staffed tablet interface or your own visitor-registration application. The capture interface and downstream system connections are implemented by your team.
Glare, blur and cropped edges can make a document difficult to read. Supported capture feedback lets your interface suggest a correction while the visitor is still at reception.
When the same document needs another photo, add the retake to its existing session. Confidence information and the structured result help staff see which details are ready for review and which still need attention.
Have an alternative registration process for unsupported documents or unresolved extraction. A scan result is information for your reception workflow, rather than an admission verdict.
Use the IdScanly REST API from your backend and keep credentials server-side. Your integration maps the returned fields to your visitor system and controls which values are sent to badge or access software.
Test the identity documents common among your visitors before rollout. Confirm the fields you need, the capture conditions at reception and how your system handles interrupted or incomplete scans.
Define access to visitor information and retention for visit records in your own systems. IdScanly processes document images for OCR rather than operating a document archive; review the current terms for temporary processing and result-retrieval data.
Read the API documentationNo. IdScanly returns document data. Your access system handles admission decisions and any door-control action.
Yes. Your application can compare extracted name fields with the appointment record and show differences for reception review.
Your integration can pass approved fields to your badge system. Badge generation and printing are implemented in your visitor-management workflow.
No. Those require separate capabilities. The API described here reads information from supported document images.
Use supported capture feedback to request a better image where appropriate. If the document remains unsupported or incomplete, follow your site’s alternative registration and security-review process.
No. Select the information required for your registration purpose and apply your site’s access and retention rules. Badge printing usually needs only a subset of the visitor record.
Try the documents your visitors commonly present. Share your visitor-management system, required fields and reception process to discuss how structured document data can fit your existing software.
Related: Hospitality guest registration · Document OCR for onboarding