Using the API

API access is available on Agent Enterprise. See plans and pricing.

What it’s for

Direct programmatic access, for when you need FeedbackRobot to be part of a system rather than a destination:

• Pushing customers into FeedbackRobot from your own database as they transact
• Pulling feedback and sentiment into your own reporting or data warehouse
• Triggering surveys from events in your own application
• Syncing resolution outcomes back into a CRM or helpdesk

If you’re trying to ask questions of your data rather than integrate systems, the MCP server is usually the better route and is available on every plan.

Authentication

Requests authenticate with an API key generated in your workspace settings.

Treat keys as credentials:

• Store them in environment variables or a secrets manager, never in source code
• Never commit them to a repository, public or private
• Never send them to us or anyone else — we will never ask for one
• Use separate keys per integration so one can be revoked independently
• Rotate them if you suspect exposure

Before you build

Two things worth deciding early:

What’s the source of truth for customer identity? If your system and FeedbackRobot both hold customer records, decide which wins before you have two versions of the same person.

What happens when the API is unavailable? Queue and retry rather than dropping. Feedback events you fail to send are gone.

Rate limits

Requests are rate limited. Build with backoff and retry rather than assuming every call succeeds immediately.

Getting started

If you’re on Agent Enterprise and setting up API access, contact us — we’ll get you the current endpoint documentation and help you scope the integration.

Alternatives worth considering first

Many things people plan to build with the API are already covered:

• Getting customers in — import your customers or a direct integration
• Getting feedback out — export, or the MCP server
• Reacting to events — automations

Check those before writing code.