Scoped API keys
Separate read and write permissions and revoke individual credentials.
LINKTIMER GUIDE
Business workspaces can create scoped API keys and use a versioned HTTP endpoint for managed-link workflows.
Separate read and write permissions and revoke individual credentials.
Use /api/v1/links for creation, listing, updates, and deletion.
Verify HMAC signatures on created, opened, updated, and deleted link events.
Create a time-limited customer link when a record reaches a workflow stage.
List and manage workspace links from an operations dashboard.
Receive signed link-open notifications at a controlled endpoint.
Use repeated API requests with idempotent application logic.
Choose required scopes and copy the secret once.
Use Bearer authentication over HTTPS.
Compute HMAC SHA-256 over the exact request body.
API keys and webhook secrets are credentials. Store them in a secret manager, rotate them, and never expose them in browser code or public repositories.
Use https://linktimer.net/api/v1/links after the hosting rewrite is deployed.
The full key is returned only when created; later screens show a prefix.
LinkTimer sends an x-linktimer-signature header using HMAC SHA-256.
Yes. Revocation stops future authenticated requests.
These links provide additional context from the destination provider or recognized security resources. External sites are responsible for their own content and policies.
Choose the expiration rule, confirm the destination, and share the generated LinkTimer URL or QR code.
Open the LinkTimer creator