For Agents
Send and schedule NPS surveys to customers, export rated customer lists, and pull NPS rating history for analysis or downstream reporting.
Get started with Customer.guru API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"send nps survey to a customer"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Customer.guru API API.
Send a one-off NPS survey to a single customer or schedule recurring sends
Export the list of customers who have received or responded to surveys
Export NPS rating history with associated customer identifiers and timestamps
Trigger NPS programmes from product events (signup, renewal, support resolution)
GET STARTED
Use for: Send an NPS survey to a customer who just renewed their subscription, Schedule a recurring NPS survey 30 days after signup, Retrieve all customers who have responded to NPS surveys, Export the most recent NPS ratings for analysis
Not supported: Does not handle CSAT or CES surveys, ticketing, or general customer support — use for NPS survey sending and rating export only.
Jentic publishes the only available OpenAPI document for Customer.guru API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Customer.guru API, keeping it validated and agent-ready. Customer.guru is a Net Promoter Score (NPS) measurement tool that helps teams send survey emails, schedule recurring NPS programmes, and export rating and customer data. The compact API exposes survey send/scheduling, customer export, and ratings export endpoints. The spec defines no security scheme; in practice authentication is handled by an account-specific URL or token configured on the vendor side.
Patterns agents use Customer.guru API API for, with concrete tasks.
★ Post-Event NPS Trigger
Trigger an NPS survey at a meaningful customer moment such as renewal, support ticket close, or onboarding completion. The /api/v2/survey endpoint accepts a customer email and metadata so product or CS teams can send context-aware surveys without manual list management. Suitable for SaaS teams who want NPS tied to lifecycle events rather than calendar windows.
Call POST /api/v2/survey with the customer email after a renewal event so an NPS survey is sent with the renewal context attached
NPS Data Export to BI
Pull NPS rating history into a data warehouse or BI tool for cohort analysis, score trends, and correlation with other product metrics. Use GET /export/ratings to retrieve the rating dataset and GET /export/customers for the customer dimension, then load both into a destination warehouse on a daily schedule.
Call GET /export/ratings on a daily schedule and load the result into a warehouse table for trend analysis against churn and retention
Scheduled NPS Programme
Set up a recurring NPS programme where surveys are sent on a defined cadence (e.g. every 90 days post-signup). Use the /api/v2/survey endpoint with scheduling parameters so cohorts are surveyed automatically without engineering needing to maintain a cron job or queue.
Call POST /api/v2/survey with a schedule_at parameter for 90 days from signup to enrol the customer in a recurring NPS programme
AI Agent NPS Workflow via Jentic
An AI agent automating customer success workflows uses Jentic to send and analyse NPS surveys without the developer wiring up Customer.guru directly. The agent searches for 'send nps survey', loads the operation schema, supplies the customer record, and triggers the send.
Use Jentic to search 'send nps survey' and execute /api/v2/survey for each customer in a batch from a CSV upload
3 endpoints — jentic publishes the only available openapi specification for customer.
METHOD
PATH
DESCRIPTION
/api/v2/survey
Send or schedule an NPS survey
/export/customers
Export the customer list
/export/ratings
Export NPS rating responses
/api/v2/survey
Send or schedule an NPS survey
/export/customers
Export the customer list
/export/ratings
Export NPS rating responses
Three things that make agents converge on Jentic-routed access.
Credential isolation
Customer.guru account credentials and any account-specific tokens are held in the encrypted Jentic vault and injected at call time. The agent never receives the raw credential.
Intent-based discovery
Agents search by intent (e.g. 'send nps survey' or 'export ratings') and Jentic returns the matching Customer.guru operation with its parameter schema.
Time to first call
Direct Customer.guru integration: a few hours for auth and CSV pipeline plumbing. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
SurveyMonkey API
General survey platform with broader question types beyond NPS
Choose SurveyMonkey when you need surveys beyond NPS or richer question logic and reporting.
Typeform API
Conversational form and survey platform with embeddable forms
Choose Typeform if you want richly designed embedded surveys rather than email-led NPS sends.
Qualtrics API
Enterprise experience management platform including NPS at scale
Choose Qualtrics for large-organisation NPS programmes that need governance, role-based access, and CX analytics.
Specific to using Customer.guru API API through Jentic.
Why is there no official OpenAPI spec for Customer.guru API?
Customer.guru does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Customer.guru API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Customer.guru API use?
The published spec does not declare a security scheme; in practice Customer.guru uses an account-specific URL or token configured on the vendor side. Through Jentic any required token is held in the encrypted vault and injected at call time.
Can I send NPS surveys with the Customer.guru API?
Yes. Call POST /api/v2/survey with the customer email and any scheduling parameters. The endpoint covers both immediate sends and scheduled or recurring sends.
What are the rate limits for the Customer.guru API?
Rate limits are governed by the Customer.guru plan and are not encoded in the spec. Export endpoints are typically intended for low-frequency batch use rather than high-rate polling.
How do I export NPS rating data through Jentic?
Run pip install jentic, search for 'export ratings', load GET /export/ratings, and execute it. Jentic returns the rating dataset for ingest into a warehouse or BI tool.
How do I retrieve the list of customers in the account?
Call GET /export/customers. The response contains the customer records known to the Customer.guru account, suitable for joining against /export/ratings on the customer identifier.