Bikeep Developer Guides

Build integrations with Bikeep smart bike parking, IoT locker, and bike room access control hardware. Authenticate, discover devices, send commands, and monitor state — everything you need to go from API credentials to a working integration.

Get Started →
Quick Start
Quickstart
Get your first API response in under 5 minutes. Authenticate, list locations, and send a device command.
Authentication
S2S OAuth2, External Users, and Public Access methods for the Bikeep API.
What Hardware Are You Integrating?
Lockers or Bike Docks
Standalone smart lockers or outdoor bike dock stations — same API, same guide.
Bike Houses (Dockless)
Enclosed bike rooms or hangars with controlled door access — no interior devices.
Bike Houses (with Docks/Lockers)
Enclosed bike rooms with door access and interior storage devices (lockers or bike docks).
Availability Data Only
Read-only location and availability data for maps, dashboards, or third-party apps. No auth required.
Concepts
Device Types
Lockers, gateways, doors, and docks — understand the hardware.
Location Types
Bike lockers, bike houses, hangars, and docks.
State Machines
Device states, commands, and transition diagrams for every device type.
Glossary
Definitions of all Bikeep API terms — bike docks, lockers, bike houses, whitelists, and more.
Reference
Webhooks
Receive real-time notifications for connectivity and alarm events.
API Reference
Full OpenAPI specification with all endpoints, request/response schemas.

What Can You Build?

Bikeep provides smart bike parking and IoT access control hardware for cities, campuses, and transit hubs. The API gives you full control:

  • Bike parking API — Reserve, lock, and unlock smart lockers and bike docks from your application
  • Bike room access control — Manage RFID allowlists for enclosed bike rooms, hangars, and secure storage
  • Availability displays — Show real-time bike parking availability on campus maps, city dashboards, or mobile apps
  • IoT monitoring — Track device health, connectivity, and alarms across your fleet

Getting Credentials

To start using the Bikeep API, you need:

  1. API credentials — A client_id and client_secret for OAuth2 authentication
  2. Operator ID — Your organization’s UUID in the Bikeep system

Request credentials by emailing info@bikeep.com.