Loading your account…
Create independent logs, fixed-message Action Keys, and optional public Read Keys. QR codes are generated automatically for Read Keys and Action Keys. Calling devices need only HTTPS — no JavaScript required.
Each log gets its own resettable Write Key. A public Read Key is optional.
Account created:
Loading…
| Timestamp | Log | Message |
|---|
Create an opaque URL for a fixed message. The calling device does not need JavaScript and never receives the log's Write Key or the configured message.
After saving, LogByLink generates /main/a/ACTION_KEY. The Action Key is itself a bearer credential, so anyone with that URL can trigger this fixed message until you regenerate, disable, or delete the key.
Actions run after a successful write and do not block logging.
LogByLink POSTs JSON and includes an x-logbylink-event-id header. Private/reserved network destinations are blocked.