API Reference

Authentication

Dashboard API requests are authenticated with a bearer token. Pass it in the Authorization header on every request:

Authorization: Bearer <your_token>

The organization is always derived from your token, never from the request body, so you can only ever read and write data within your own org. Embed tokens used by the widget are a separate, HMAC-signed credential and are not interchangeable with dashboard bearer tokens.

Base URL

All endpoints are versioned and served from a single base URL:

https://api.getfeedforward.com/v1

Endpoints

A representative selection of the resources you can work with:

• GET /v1/surveys — list the surveys in your organization.
• POST /v1/surveys — create a new survey with its questions.
• GET /v1/responses — page through collected responses, including AI insights.
• GET /v1/analytics/overview — aggregate metrics (NPS, CSAT, response volume).

Example request

Fetching your surveys with curl:

curl https://api.getfeedforward.com/v1/surveys \
  -H "Authorization: Bearer $FEEDFORWARD_TOKEN" \
  -H "Content-Type: application/json"

Rate limits

API requests are rate limited per token. Standard plans allow up to 600 requests per minute; on-demand AI endpoints (such as question suggestions) carry a tighter per-user limit. When you exceed a limit the API responds with 429 Too Many Requests and a Retry-After header indicating how long to wait before retrying.

New here? Start with the documentation for setup and core concepts.