API tokens
Get an API token for your software, and keep it safe.
An API token lets your software use the API. Each token belongs to a bot, a Standard member of one church. Whatever uses the token acts as that bot, not as the person who created it, and can only see and do what that bot can.
Get a token
- A church admin creates a bot under Settings → Developers.
- The admin creates a token on the bot. It’s shown once, and it starts with
ccb_. - Someone who can add people to a chat adds the bot under Chat settings → Developers, choosing whether it can post or only read.
A new bot is in no chats, so its token can’t read or post anything until step 3. The API reference shows how to send it.
What a token can reach
A token can read and post in its bot’s chats, react, and upload files. It can’t change invites, churches or membership, so a bot can’t give itself more access.
Within its chats, the same rules apply to a bot as to a person. It sees only the people in them where the chat allows that. See who can see what.
Keep tokens safe
Anyone holding a token can read every chat its bot is in. Keep it in your server’s or your assistant’s settings, never in a web page or mobile app.
When the admin who created a token stops being an admin, or leaves your church, the token stops working in case it was copied, and the other admins get an email naming the bots that need a new one.
A bot can have several tokens, which lets you replace one without downtime: create a new token, start using it, then revoke the old one. Revoking a token ends its access at once, and deactivating a bot ends access for all its tokens.