Turnstile setup token

Generate a token

In your Cloudflare Turnstile widget, add docs.akedly.io to Hostnames. Open the link printed by the CLI: its siteKey query parameter contains only your public site key. Keep the secret key in a private file on the machine running the CLI.

If the link has no site key, include --turnstile-site-key <public-site-key> in your command to get a populated link. The helper shows the site key it is using, so you can check it matches your Cloudflare widget. It refuses a key that looks like a secret key and removes it from the address bar; if that happens, rotate the secret key in Cloudflare.

The challenge uses the setup action akedly_setup. This page contacts Cloudflare to generate the token; it does not submit the token to Akedly, save your settings, send a message or store the token. Akedly accepts CLI setup tokens only from docs.akedly.io.

Save your keys

Replace the placeholders with your pipeline id, public site key, private secret-file path and the token above:

akedly pipelines update <id> --turnstile on --turnstile-platform web --turnstile-site-key <public-site-key> --turnstile-secret-key-file <private-file> --turnstile-test-token <fresh-token> --yes

Tokens expire after five minutes and can be used only once. Generate a fresh token after a refused or uncertain save. The backend verifies the token with your secret key and checks the hostname and setup action before saving the integration.

This setup token is for --turnstile-test-token. Sending an OTP uses a separate end-user token through --turnstile-token.

Next: connect your own Turnstile keys or see the pipeline command reference.