Control your apartment or condo buzzer with a REST API.
Timed unlocks, guest passcodes, and recurring schedules.
Works with call boxes that dial a phone number. Your building must forward calls to your Lowkey number and you must test at the entrance.
After subscription activation, we provision a Lowkey phone number. Ask your building manager to set it as your unit’s call-box destination.
Sign in with an email code and create a scoped API key for your agent or application. Keep the key in its secret settings.
Set a timer for your next delivery. Create a passcode for tonight's guests. Premium also supports recurring schedules. Test the buzzer before relying on any rule.
Expecting a delivery? Create a 30-minute timer rule. When the driver calls your configured unit during that window, Lowkey can accept the call. Test your building’s door-release tone first.
Create a four-digit visitor passcode for a guest booking, with a use limit and expiry. On the Multi Building plan, one parent-account key can manage your linked building numbers with explicit building selection.
On Premium, schedule an access window for a regular visitor such as a dog walker. Revoke the rule when plans change.
Use a scoped API key from your application or agent to create and revoke access rules for a connected unit. Subscription and physical setup are required.
Connect an automation platform that can make HTTP requests to the BuzzerAPI service. Keep your access key secret and apply the same visitor approval rules you use manually.
Expecting a package or food delivery? Create a timed access window. When the driver dials your configured unit, Lowkey can accept the call during that window.
Friends coming over? Create a four-digit code with an expiry and use limit. They dial your unit, then enter the code when prompted. Test it at the building entrance first.
Premium supports weekly access windows for regular visitors. Review and revoke schedules when your needs change.
The Lowkey app supports household sharing on eligible plans. Agent API keys are scoped separately from billing and account setup.
Review recorded buzzer events and access attempts with timestamps. A call record does not verify that a visitor physically entered.
Configure a webhook for supported buzzer events and receive signed deliveries at your HTTPS endpoint.
Use the Lowkey app or API logs to review recorded access activity. Physical entry must be verified at the building.
Manage guest access across linked buildings on the Multi Building plan. Select each building explicitly in the API or CLI; its rules, logs, and callbacks stay separate.
For deliveries, guests, cleaners, and dog walkers, your agent can create a timed access window or a four-digit visitor code for a phone-based apartment or condo call box. You control the subscription, building setup, and scoped API key.
Compare current prices, sign in with email, and finish Stripe hosted checkout.
Set the building call box to your provisioned phone number and test a real call.
Create a scoped agent key and put it in the connector’s secret settings.
Current monthly and yearly prices come directly from Lowkey’s Stripe plans. Your subscription must activate before access can be created. Cancel or change an existing plan in the billing portal.
Timed access windows and visitor passcodes for one configured buzzer number. Monthly and yearly billing available.
Loading current prices…
Sign in & subscribe →Timed access, visitor passcodes, and weekly routines for one configured buzzer number. Monthly and yearly billing available.
Loading current prices…
Sign in & subscribe →Managing multiple buildings? Subscribe to Multi Building in the Lowkey app, then add, remove, and control each building through the API or CLI.
After subscription activation, create a scoped agent key in your account. A new access rule requires an Idempotency-Key so a retry cannot silently create a second rule. Use your connected service origin; the public API hostname will be enabled when the backend launches.
curl -X POST "$BUZZER_BASE_URL/v1/unlock" \
-H "Authorization: Bearer $BUZZER_API_KEY" \
-H "Idempotency-Key: your-stable-request-id-1234" \
-H "Content-Type: application/json" \
-d '{"type":"timer","duration_minutes":15,"label":"Package delivery"}'
Need visitor access instead? Use type: passcode with an optional one-to-four-digit code, an expiry, and a use limit. The API generates a four-digit code when you omit it. Weekly routines require Premium. Test the call box before trusting any rule.