Customer Feedback API — Trigger Surveys from Any System
FeedbackRobot's API skill lets you trigger surveys programmatically from any platform, app, or workflow — if it can make an HTTP request, it can send a FeedbackRobot survey.
Why it matters
Not every business runs on Shopify, Stripe, or Salesforce. Some use custom-built CRMs, in-house order management systems, bespoke booking platforms, or legacy ERPs that have no native FeedbackRobot integration. The API skill is built for exactly these cases — a direct, flexible interface that lets any system trigger a FeedbackRobot survey with a single HTTP request.
With a POST request to FeedbackRobot's survey trigger endpoint, your system passes the customer's contact details, the survey template ID, and any metadata relevant to the feedback context — order ID, product category, service type, account tier. FeedbackRobot handles delivery, collection, and reporting automatically. Your system fires the trigger. FeedbackRobot runs the feedback loop.
For developer-led teams building customer experience tooling on top of FeedbackRobot, the API enables more advanced workflows: conditional survey routing based on customer segment, integration with data warehouses for response analysis, and attribution of feedback to specific business events. The API is also the recommended path for businesses that need to send surveys from multiple systems and want a single integration point rather than multiple native skill connections.
About
API
The FeedbackRobot API is designed for engineering teams that need flexibility beyond what native integrations provide. Every native FeedbackRobot integration — Shopify, Stripe, Cin7, Salesforce — is built on the same survey trigger API that's available to you directly. This means anything a native integration can do, you can replicate and extend via the API.
For businesses with custom-built platforms — proprietary booking systems, in-house CRMs, bespoke fulfilment software — the API is often the only practical path to automated feedback collection. It removes the dependency on native integrations entirely: as long as your system can make an outbound HTTP request, it can trigger a FeedbackRobot survey at any event you define.
The API also supports passing arbitrary metadata with each survey trigger. This metadata is attached to the response record in FeedbackRobot and available for filtering and export — enabling you to segment feedback by any dimension your system tracks, not just the dimensions FeedbackRobot natively understands.
SETUP
How it works
Enable the API skill in Settings → Skills and generate your API key
Make a POST request to the survey trigger endpoint with the customer's contact details, survey template ID, and any metadata
FeedbackRobot delivers the survey and collects the response automatically
Responses flow into your Radar inbox like any other integration — filtered by source, segmented by sentiment
BENEFITS
What you get
Trigger surveys from any system that can make an HTTP request — no platform dependency
Pass custom metadata to attribute feedback to specific events, orders, or customer segments
Full API documentation with code examples for common use cases and languages
Same response dashboard as all other FeedbackRobot integrations — no separate tooling
Ideal for custom platforms, legacy systems, and multi-source survey orchestration
FEATURES
Everything you need to manage reviews at scale.
AI-generated responses
Multi-platform dashboard
Automated alerts
FAQ
Frequently
Asked Questions
What does a basic API survey trigger request look like?
A POST request to /api/v1/surveys/trigger with the customer's email, name, the survey template ID, and optional metadata key-value pairs. Full documentation with code examples in Python, JavaScript, Ruby, and cURL is available in the FeedbackRobot developer docs.
Is there rate limiting on the survey trigger API?
Yes. Rate limits vary by plan. For high-volume use cases — bulk sends or high-frequency event triggers — contact our team. For large one-time send operations, the Customer Import skill may be more appropriate than individual API triggers.
Can I pass custom metadata with an API trigger?
Yes. Pass any key-value metadata pairs with your trigger request. This data is attached to the survey response in your dashboard and available for export and filtering — letting you segment feedback by any dimension your system tracks.
What authentication method does the API use?
The FeedbackRobot API uses API key authentication. Generate your key from Settings → Skills → API. Treat it like a password — do not expose it in client-side code or public repositories.
INTEGRATIONS
Works with the platforms you already use
INDUSTRIES
Works with the platforms you already use
Hospitality & Travel
Automate guest feedback to boost satisfaction, improve loyalty, and enhance every stay.
Events & Entertainment
Capture attendee feedback to refine experiences, improve follow-ups, and grow event engagement.
Food & Beverages
Collect and act on diner feedback to improve experiences, menus, and customer satisfaction.
