Groups.io

Last reviewed: July 2026

Overview

Integuru's Groups.io integration provides production-ready HTTP API access to Groups.io, the mailing list and community platform used by professional associations, water utilities, environmental groups, and specialist communities, covering 3 actions: dl, get_topic_messages, and search_groups.

No official API. Groups.io does not publish a developer API. Bulk access to message archives previously required manual browsing or fragile scraping scripts that broke on login page changes. Integuru handles session management, authentication, and pagination automatically.

All three actions carry full API documentation with richer reference available:

• dl: Bulk download messages from multiple groups, up to 200 messages per group by default (10 pages at 20 messages each).
• get_topic_messages: Retrieve all messages in a specific thread by thread_id and group_name.
• search_groups: Discover publicly listed groups by keyword, returning up to 1,000 results (50 pages at 20 per page).

Teams use this integration to ingest community discussions at scale, whether for research, AI training data pipelines, or monitoring specific topic threads. See YC Bookface for another community platform integration, or browse the full integrations catalogue.

---

Use Cases

Integuru's Groups.io integration lets your team download message archives, retrieve full conversation threads, and discover groups programmatically across the platform's public community catalog.

Resumable pagination: The start_group and start_page parameters let you checkpoint a long-running dl job. When a response is partial, it returns next_start_group and next_start_page. Pass those values on your next call and groups before start_group are skipped entirely, so the run continues from exactly where it stopped without re-fetching completed groups.

• Bulk archive download: Use dl to fetch messages from multiple groups in a single call. The action defaults to 10 ICP groups covering water utility and environmental topics, returning up to 200 messages per group (10 pages at 20 messages per page).
• Thread retrieval: Call get_topic_messages with a thread_id and group_name to pull all messages in a specific topic. Sort order defaults to oldest-first (asc); pass desc to reverse.
• Group discovery: Use search_groups to find publicly listed groups by keyword. It returns 20 results per page and defaults to fetching 50 pages, giving you up to 1,000 matching groups per query.

---

Setup Notes

Integuru's Groups.io integration authenticates against groups.io/. Integuru manages the login session automatically, so you do not need to handle cookies or session tokens yourself.

The dl action ships with its own defaults, each of which you can override per call:

• groups: Defaults to 10 ICP groups covering water utility and environmental topics. Pass your own array of group names to target different communities.
• max_pages_per_group: Defaults to 10, giving you 200 messages per group (20 messages per page). Increase this to ingest deeper archives.
• start_group: Defaults to 0 (the first group in the array). Set this to the next_start_group value from a previous partial response to resume a run.
• start_page: Defaults to 0. Set this to the next_start_page value from a previous partial response to continue from the exact page where the prior run stopped.

For large archive jobs that span many groups, check the response for next_start_group and next_start_page, then pass those as start_group and start_page on your next call. Groups before start_group are skipped entirely, so you can continue a partially completed run without duplicating work.