For Agents
Read and write community content, users, and gamification on a Gainsight (inSided) community - articles, topics, ideas, events, badges, and federated search.
Use for: I want to publish a new article in our customer community, Search community topics for posts mentioning a specific feature, List all open ideas submitted by customers in the last 30 days, Award a community badge to a top-contributing user
Not supported: Does not handle CRM contact records, support ticketing SLAs, or marketing email sends - use for community content, users, and gamification only.
The Gainsight Customer Communities API (formerly inSided) lets product, support, and community teams programmatically manage online communities, including topics, articles, conversations, questions, ideas, product updates, events, gamification, and federated search. Gainsight publishes its own OpenAPI documents for this API on its Customer Communities API documentation portal, split across five files; Jentic maintains a curated, agent-optimized specification that merges that set into one validated document. The 324-endpoint surface covers content moderation, user and group administration, badge and reputation programmes, and analytics, so agents can keep a community in sync with adjacent systems such as a CRM or knowledge base. Calls are scoped to the customer's community subdomain and authenticated via OAuth 2.0.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gainsight Customer Communities API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finsided.com%2Finsided" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finsided.com%2Finsided" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Gainsight Customer Communities API.
Publish and reply to community articles and conversations through the /v2/articles and /v2/topics endpoints
Capture and triage product feedback as ideas with status changes, votes, and comments
Run federated search across community content with /v2/search and surface results to agents
Manage gamification programmes by awarding badges, ranks, and points to community users
GET STARTED
Schedule and update community events, including registrations and event types
Moderate content with moderator tags, post locking, and bulk user actions
Patterns agents use Gainsight Customer Communities API for, with concrete tasks.
★ Customer Idea Triage Pipeline
Pull new community ideas from /v2/ideas, attach votes and comments, and forward them into a product backlog so customer-driven feature requests reach the roadmap without manual copy-paste. The API exposes idea status transitions and merge operations, so an automation can keep both the community and internal tracker in sync as ideas progress.
List ideas updated in the last 24 hours, fetch their vote counts and top comments, and create matching tickets in the configured product tracker.
Community Knowledge Search for Support Agents
When a support agent opens a ticket, surface relevant community articles and answered questions by hitting /v2/topics/search and /v2/search with the ticket subject. This shortens resolution time by reusing community-validated answers instead of re-investigating each issue, and the federated search endpoint covers articles, conversations, and questions in one call.
Run /v2/search with the customer's question and return the top three matching articles or answered questions with their URLs.
Gamification and Recognition Program
Reward power users by automatically awarding badges and rank changes through the gamification endpoints when they hit thresholds - number of accepted answers, ideas submitted, or events attended. The community then renders badges on profiles, increasing engagement without manual community-manager work.
Identify users who reached 10 accepted answers this month and POST a badge grant for them via the gamification endpoint.
AI Agent Community Operator via Jentic
An AI agent with access to this API through Jentic can monitor, classify, and respond inside the community on behalf of a community manager. Jentic handles the OAuth token lifecycle and exposes each operation by intent, so the agent can move from listing unanswered questions to drafting replies and applying moderator tags without touching the raw API surface.
Through Jentic, call the search-unanswered-questions and post-reply operations to draft a reply on the oldest unanswered question and apply a 'needs-review' moderator tag.
324 endpoints — the gainsight customer communities api (formerly insided) lets product, support, and community teams programmatically manage online communities, including topics, articles, conversations, questions, ideas, product updates, events, gamification, and federated search.
METHOD
PATH
DESCRIPTION
/v2/topics
List community topics
/v2/topics/search
Search topics by query
/v2/articles/create
Create a community article
/v2/articles/{id}/publish
Publish an article
/v2/articles/{id}/reply
Reply to an article
/v2/articles/{id}/like
Like an article
/v2/topics
List community topics
/v2/topics/search
Search topics by query
/v2/articles/create
Create a community article
/v2/articles/{id}/publish
Publish an article
/v2/articles/{id}/reply
Reply to an article
/v2/articles/{id}/like
Like an article
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Gainsight Customer Communities API by hand means running the OAuth 2.0 client credentials flow to mint tokens and mapping its content and gamification endpoints on the api2-us-west-2 host yourself. Through Jentic you install once, import the Gainsight Customer Communities API from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
This API puts the article id in the URL path (/v2/articles/{id}/publish), so a rule can pin your agent to publishing or replying on one article. You choose the operations it may call, so liking or creating articles is not included unless you add them.
Credential isolation
Your OAuth 2.0 client credentials for the Gainsight Customer Communities API are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search community articles' or 'reply to a community topic', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the 324 documented paths.
Alternatives and complements available in the Jentic catalogue.
Specific to using Gainsight Customer Communities API through Jentic.
Which OpenAPI specification does this Gainsight Customer Communities API page describe?
A curated, agent-optimized Jentic specification covering 324 Gainsight Customer Communities operations in a single document. Gainsight also publishes its own OpenAPI documents for this API, indexed on its Customer Communities API documentation portal at https://api2-us-west-2.insided.com/docs/ and split across five files: Community API, User API, Events API, Search API, and Gamification API, 344 operations in total. The Jentic variant merges that document set into one validated OpenAPI 3.0.3 file, so an agent can search every community operation without picking a file first. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Gainsight Customer Communities API use?
The API uses OAuth 2.0 under the insided_auth scheme. You exchange client credentials for an access token and pass it in the Authorization header on each request. Through Jentic, the OAuth credentials sit in your encrypted Jentic One instance and the access token is injected at execution time, so the agent never sees the secret.
Can I publish articles and reply to threads with this API?
Yes. POST /v2/articles/create creates a new article, POST /v2/articles/{id}/publish moves it to live, and POST /v2/articles/{id}/reply posts a reply. Equivalent endpoints exist for conversations and questions, so an agent can manage the full content lifecycle end to end.
What are the rate limits for the Gainsight Customer Communities API?
The OpenAPI specification does not encode explicit rate limits. Plan for community-scale throughput, batch list calls instead of per-item polling, and back off on 429 responses; rate-limit ceilings are typically set per community subscription, so check with Gainsight for the exact numbers.
How do I search community content for a support ticket through Jentic?
Install with pip install jentic, then run the search-load-execute flow with a query like 'search Gainsight community for a topic'. Jentic returns the federated search operation backed by /v2/search; pass the ticket subject as the query and the agent receives ranked articles, questions, and conversations.
Can the API award badges and ranks automatically?
Yes. The gamification endpoints expose badge grants, rank assignments, and leaderboard reads, so an automation can listen for events such as accepted answers and POST a badge grant when thresholds are met.
Can I limit what my agent is allowed to do with the Gainsight Customer Communities API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can grant only what a given task needs. This API puts the article id in the URL path, as in POST /v2/articles/{id}/publish, so a rule can pin the agent to publishing or replying on a single article. If you do not add liking, article creation, or the gamification and moderation endpoints, the agent cannot call them.