Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks and API tokens

Send event notifications to your systems and create API tokens for programmatic access.

What it is

Webhooks push selected events from klink.cloud to an HTTPS endpoint you control. API tokens authenticate API clients with scoped abilities (permissions) and optional expiry. Both are admin developer tools under Settings.

For payload shapes, signature headers, and automation platform examples, use the full Webhook Integration Guide. This page is the Settings admin summary.

Create a webhook

  1. Go to Settings, then Webhooks.

  2. Create a webhook.

  3. Choose Development or Production.

  4. Enter the endpoint URL.

  5. Pick authentication as required by your receiver.

  6. Select the events to send.

  7. Save. Use the signing secret to verify requests. Check Delivery logs when troubleshooting.

Treat the signing secret like a password. Rotate it if it may have leaked, and update your receiver to use the new secret.

Create an API token

  1. Go to Settings, then API Tokens.

  2. Create a token.

  3. Set abilities (scopes) and an optional expiry.

  4. Copy the token immediately. It is shown once.

  5. Store it in your secret manager. Do not commit it to source control.

Rotate, revoke, or delete

  • Rotate a token when you need a new secret without losing the ability set (then update clients).

  • Revoke or delete a token to cut off access immediately.

Related pages