Gainsight Customer Communities API

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 the encrypted Jentic vault 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.