01
Log from almost anything
Read Keys and Action Keys get scannable QR codes automatically. Use them with NFC tags, bookmarks, sensors, home automation, or any device that can open an HTTPS URL.
URL-driven logging
A URL can be a button.
Open a link and LogByLink records an event. No app, SDK, webhook client, or JavaScript is required on the calling device.
HTTPS
Resettable keys
Optional public reads
Simple GET requests
Dynamic write
logbylink.com/main/WRITE_KEY/fed-the-dog
↓
OKfed-the-dog · just now
Fixed-message Action Key
logbylink.com/main/a/ACTION_KEY
The Write Key and message stay server-side.
02
Keep reads private
Use an optional Read Key, an account-wide Parent Read Key, or disable public reads entirely and view everything only in your signed-in dashboard.
03
Reset access without losing history
Write Keys, Read Keys, Parent Read Keys, and Action Keys can be regenerated independently. Historical log entries stay attached to the permanent log instance.
How it works
Three steps. No client library.
1. Create a log
The dashboard generates a cryptographically random Write Key.
2. Build a URL
Use a dynamic Write Key URL, or create an opaque Action Key for a fixed message.
3. Open it
LogByLink validates the capability, records the timestamped value, rate-limits abuse, and returns OK.
For simple devices
Hide the Write Key and message with an Action Key.
For a repeated fixed event such as fed the dog, filter changed, or door opened, create an Action Key in the dashboard. LogByLink immediately creates a scannable QR code for it.
The public device receives only an opaque URL. The real Write Key and configured message are stored server-side.
Action Keys are bearer credentials. Anyone who has the Action Key URL can trigger its fixed message until you regenerate, disable, or delete that key.
Dynamic message
/main/WRITE_KEY/message
Use when the caller supplies the value.
Fixed message
/main/a/ACTION_KEY
Write Key + message remain server-side.
Read one log
/main/READ_KEY
Optional. Dashboard-only mode is supported.
Designed for capability links
Simple on the device. Deliberate on the server.
HTTPS in transit. Request paths are encrypted between the caller and the TLS endpoint.
Hashed lookup. Public capability values are hashed for authorization lookup.
Immediate revocation. Regenerated, disabled, or deleted keys stop authorizing new calls.
Replay suppression + rate limits. Short accidental repeats are suppressed and abusive call rates are constrained.
No public read required. Keep logged values visible only in the authenticated dashboard if you prefer.
Turn a link into a log entry.
Create a log, copy a URL, and call it from almost anything.