Link API Documentation
Link is Last Lock's primary way of communicating with locks.
External API Scope
This documentation covers externally available Link APIs only:
proto/org.proto(Org service)proto/sil.proto(SIL service used for integration testing)
Below, you’ll find an overview of different API sections to help you integrate and manage operations efficiently.
Start here:
- How Link Works for Org API integration flow
- SIL Service for SIL test API usage
- Authentication for external auth expectations
- Aliro API for public Aliro operations
- Credential Profiles for generic DESFire credential-profile operations
Link overview
Link allows you to assign credentials and monitor Last Lock locks. Every Last Lock device is assigned, at creation, a Device ID. Talk to your contact at Last Lock if you are unsure of your device's ID. You can use this ID to assign credentials to your lock. You can also use this ID to monitor attempted access to your lock.
Prerequisites
- Obtain a valid Last Lock API key from your Last Lock contact.
- Obtain your organization-specific URL from your Last Lock contact.
- Clone the Seamless Link Repository from GitHub:
git clone https://github.com/last-lock/seamless-link.git - Compile the protobuf files
- For more on Protocol Buffers, see the official documentation: Protocol Buffer documentation
- Instructions for compiling protobufs for your language are available here: Compile Protocol Buffers
Connecting to Seamless Link
The Link API communicates over gRPC. gRPC provides flexibility across languages, streaming, versioning, and efficient connection management. To access your organization's locks over Link, you'll authenticate and begin making requests over gRPC.
Full API capabilities are documented in the Seamless Link Repository
Compatibility Notes
This documentation describes the current public API behavior and calls out a few implementation details that matter when writing clients.
In particular:
- Aliro reader public keys are discovered through device summaries
- Audit stream payload shapes may grow over time
- Credential profiles are supported through the current Org API surface
Assigning credentials
Link supports a range of credential types including 125kHz Prox credentials (H10301, Corporate 1000, etc.),
NFC credentials, and mobile wallet passes.
To assign credentials to locks, use the Assign method.
The Assign method takes a map of device IDs to lists of credentials.
This declares the target credential set for each lock.
Link computes the minimal actions required to reach that state and propagates them to the lock.
For details on encoding Prox credentials, see Prox Credential Formats.
Auditing locks
Last Lock devices record every attempted access and propagate these as audits to Link. You may query the entire history of attempted access on your lock. You may also stream updates to receive pushes for each attempted access.
💡 Need Help? Contact us at support@lastlock.com.