Once you have a group tuned exactly the way you like, you don't have to rebuild that setup by hand in every other group. Telm's REST API lets you read a group's settings, moderation rules and whitelist and write them into another group, so a proven configuration becomes a template you can roll out anywhere. It's the go-to option for agencies and anyone running several communities on one policy. The full API is included on Pro and above; you drive it with an API key you create in the dashboard.
Want to set this up? Do it right in your Telm account.
Open in your dashboard1Why copy a configuration
Tuning a group well takes time — you dial in the anti-spam sensitivity, add the moderation rules that fit your community, and build up a whitelist of people who should never be touched. Recreating all of that by hand in the next group is slow and easy to get wrong.
Copying the configuration solves that. You capture a setup that already works and reproduce it in seconds. It's ideal for agencies applying one standard policy across many communities, for spinning up new chats from a template group, and for keeping a safe snapshot of a configuration you rely on.
2What you can copy
Three parts of a group define most of its behaviour, and each can be read from one group and written to another:
- Group settings — anti-spam sensitivity, welcome, language and every toggle stored in the group configuration.
- Moderation rules — the name, type, conditions, actions, priority and on/off state of each custom rule.
- Whitelist — the list of members exempted from moderation.
3How it works with the API
Telm exposes a plain REST API at api.telm.com/api/public/v1. You read from the source group and write to the target group with ordinary HTTPS requests — from any language, or straight from your terminal with curl.
For settings, you fetch them from the source group and send them to the target with a single PATCH — the values you send are merged into the target's configuration. For rules and the whitelist, you list the entries on the source group and create the same ones on the target. The mechanics, authentication and quotas are covered in The Telm REST API.
4What you need
You need an API key, which you create in the dashboard, and a plan that includes full API access — that's Pro and above. Read more in The Telm REST API.
The key inherits your access, so it can only touch groups you already manage. That keeps configuration transfers scoped to your own account.
5Practical tips
Save the responses you read from a group as plain JSON files — they're a snapshot you can re-apply at any time to roll a group back to a known-good state.
Roll out to one group first and check it before applying the same configuration across the rest. It's much easier to catch a surprise on a single chat than on twenty.
To decide which groups to keep in sync, first see Managing multiple groups.