Ingresso Platform API
A complete HTTPS + JSON access control API for condominiums, gated communities, commercial properties, industrial facilities, and government environments. Every resident, tenant, employee, visitor, vehicle, credential, entry point, and access event is reachable from your own software — no middleware, no proprietary SDK, no vendor-hosted integration layer.
If your system knows who needs access, Ingresso can already open the door or gate for them.
Apply for API Access# Query residents via simple HTTP GET curl -H "X-API-Key: $INGRESSO_KEY" \ "https://your-community.ingressosecurity.com/api/residents.php?community_id=3" // JSON Response { "success": true, "data": [ { "resident_id": 88, "first_name": "John", "last_name": "Smith", ... } ], "total": 1, "limit": 100, "offset": 0 }
Direct Core Integration
Ingresso isn't an access control system with an API bolted on the side. The API *is* the system.
Our manager portal, our resident portal, our Windows management applications, and our controller processor all talk to the exact same endpoints you will. There is no hidden internal interface, no privileged back channel, no "that feature isn't exposed yet." If Ingresso can do it, your integration can do it.
That matters, because it means the surface you build against is the surface we depend on. It doesn't get deprecated quietly and it doesn't lag behind the product.
Plain REST semantics throughout — GET to read, POST to create,
PUT to update, DELETE to remove. Filters go on the query string.
Payloads are JSON. Anything that speaks HTTP speaks Ingresso:
Comprehensive API Coverage
Full read and write control over every domain model in the platform.
Residents, properties, buildings, and units. Full lifecycle — create, update, deactivate, expire. Single aggregate call hydrates an entire resident record (profile, address, visitors, vendors, preferences) in one round trip.
Property-scoped guest lists and recurring service providers with custom start dates, expiration windows, and one-time-use passes that auto-consume after entry.
Physical Wiegand-26 access cards and QR-code passes issued through a unified credential model. Issue, revoke, flag lost/stolen, or bulk-provision. Changes queue to hardware automatically.
Who may open which door, on which days, during which hours. Weekly schedules, holiday calendars with recurring dates, and seasonal validity ranges enforced directly at the hardware panel.
Queryable history of every grant, denial, exit request, forced door, and held-open alarm. Includes incremental cursor support so you can poll for new events without webhooks or public endpoints.
Send QR passes to guests by email or SMS in one call — platform renders the code and delivers it. Supports Firebase push notifications to resident devices and transactional HTML emails with attachments.
Read real-time door state, trigger remote relay pulse/unlock, query controller health and sync status, and enqueue hardware provisioning tasks remotely.
Attendant messaging with per-resident voice recordings and verification codes, retrievable as raw audio streams for custom gatehouse or kiosk workflows.
Proven Integrations
Automate resident credential provisioning, visitor passes, vehicle tags, and gate entry directly from property management databases.
Sync tenant directories, employee keycards, visitor check-ins, and turnstile or elevator clearance based on office lease status.
Manage truck entry gates, warehouse dock doors, contractor access schedules, and perimeter security with full real-time event tracking.
Enforce strict security clearance levels, time-restricted access groups, and permanent tamper-proof audit trails across municipal infrastructure.
Build custom tablet apps, self-service kiosks, or gatehouse workflows on our visitor and event endpoints while Ingresso manages hardware.
Pull high-volume event streams into your data warehouse to monitor facility throughput, peak traffic staffing, and security incidents.
Architecture & Security
Ingresso runs a two-tier model. A master server authenticates and resolves an account to its community, then hands back that community's API hostname and key. Every data operation from that point is a direct call to the community's dedicated API server.
For an integrator, one integration scales cleanly from a single 50-unit HOA to a portfolio of hundreds of properties.
No cleartext endpoint exists across the entire Ingresso infrastructure.
Separately issued, independently revocable, and strictly attributable in audit logs.
A key grants access to its assigned community data and nothing else by construction.
Every mutating call carries actor identity and lands permanently in community logs.
Developer Onboarding
Tell us what you're building. We review every request by hand — it takes a couple of minutes to fill out and it means the key we issue is already scoped correctly for your integration. Approved requests are typically turned around within two business days.
Thanks — we've got it. Here's what happens next:
1. Review. A person on our engineering team reads your request, usually within two business days.
2. Provisioning. We create a key scoped to your integration and, if requested, a sandbox community with seed data.
3. Delivery. Your key and the full developer guide arrive by email, along with a direct contact for technical questions.
A confirmation email has been sent to your work email address.