🇫🇮 FI

🇬🇧 English EN 🇸🇦 العربية AR 🇨🇿 Čeština CS 🇩🇰 Dansk DA 🇳🇱 Nederlands NL 🇫🇮 Suomi FI 🇫🇷 Français FR 🇩🇪 Deutsch DE 🇮🇹 Italiano IT 🇯🇵 日本語 JA 🇰🇷 한국어 KO 🇵🇱 Polski PL 🇵🇹 Português PT 🇷🇺 Русский RU 🇪🇸 Español ES 🇹🇷 Türkçe TR

Create and protect API access

Create a purpose-specific export token, store its one-time value safely, and revoke it if exposed.

Tämä artikkeli ei ole vielä saatavilla kielelläsi. Alla näytetään englanninkielinen lähde.

Treat the token like a password

Export API tokens are bearer credentials. The raw value may be shown only once; Runekist stores a hash rather than the reusable secret.

Open Leadership → Access & sharing → API access.
Create one token for one integration where practical.
Copy it directly into the integration’s secure secret storage.
Verify the supported export call.
Revoke the token when it is no longer needed or might have leaked.

Never include a raw token in a screenshot, source repository, public chat, or support message.

Selaa Ohjeita