canonical: https://jentic.com/apis/feedier.com/feedier

# Feedier API

Jentic publishes the only available OpenAPI specification for Feedier API, keeping it validated and agent-ready. Feedier is a customer feedback management platform that combines surveys, NPS, testimonials, and reward distribution. The API exposes eight endpoints covering carriers (the Feedier term for surveys), feedback responses, tags, filters, testimonials, reward transactions, and SMS or email push delivery so a CX team can integrate Feedier into a CRM or trigger surveys from product events.

## For AI agents

Trigger Feedier surveys via SMS or email, list feedback responses, and read tags, filters, and testimonials from a Feedier workspace.

## Scope

Does not handle survey design, response analytics dashboards, or A/B testing - use for Feedier survey distribution, feedback retrieval, and testimonial reads only.

## Capabilities

- List configured Feedier carriers (surveys) for the account
- Read feedback responses with associated tags and filters
- Send a survey to a respondent via SMS through `/push/sms`
- Send a survey to a respondent via email through `/push/email`
- Update reward transactions on incentivised feedback
- Read published testimonials for marketing reuse

## Use cases

### Post-Purchase NPS Trigger

E-commerce teams trigger a Feedier NPS survey after a successful order. POST `/push/email` sends a personalised survey link to the buyer, GET /feedbacks pulls the responses a few days later, and tag and filter endpoints help segment promoters versus detractors so the team can route follow-up actions automatically.

Example prompt: On order-completed event, call POST `/push/email` with the customer email and the NPS carrier ID.

### SMS Feedback for Field Services

Field-service businesses collect feedback by SMS the moment a job is closed. POST `/push/sms` sends the carrier link, and GET /feedbacks pulls the structured response so the dispatcher dashboard can surface scores for each technician and trigger coaching workflows when scores drop.

Example prompt: When a service ticket is closed, call POST `/push/sms` with the customer phone number and the technician's NPS carrier ID.

### Testimonial Pipeline for Marketing

Marketing teams pull approved testimonials from Feedier into their CMS. GET /testimonials exposes the curated quotes so a website build can render fresh testimonials at deploy time without copy-paste from the Feedier dashboard.

Example prompt: Pull GET /testimonials nightly and write the active testimonials into the marketing site's content collection.

### Agent-Driven Feedback Loop

An AI agent supporting CX operations can use Jentic to discover Feedier's push, feedback, and testimonial endpoints, send surveys triggered by support resolution events, and route promoter responses into a marketing pipeline - keeping the Feedier bearer token inside your Jentic One instance.

Example prompt: Use Jentic to search 'send a feedier email survey' and execute POST `/push/email` with the customer email and carrier ID.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/push/email` | Send a survey via email |
| POST | `/push/sms` | Send a survey via SMS |
| GET | `/feedbacks` | List feedback responses |
| GET | `/carriers` | List carriers (surveys) |
| GET | `/testimonials` | List approved testimonials |
| POST | `/feedbacks/reward/transaction` | Update a reward transaction |

## Key resources

- **Carriers** — List Feedier surveys (carriers) configured on the workspace
- **Feedbacks** — Read feedback responses and update reward transactions
- **Tags** — List tags used to segment Feedier responses
- **Filters** — List filters used to query feedback subsets
- **Testimonials** — Read approved testimonials
- **Push Notifications** — Send surveys via SMS or email

## Why Jentic

- **Setup:** Wiring the Feedier API by hand means handling its bearer auth and assembling the carrier and recipient fields required to push surveys over email and SMS yourself. Through Jentic you install once, import Feedier from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Feedier takes the recipient and survey target in the request body rather than the URL path, so limit the agent to the operations it needs, such as pushing an email survey or reading feedback. You choose which operations it may call, so a write like rewarding a feedback transaction is included only when you add it.
- **Credential handling:** Your Feedier bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a Feedier email survey', and Jentic returns the matching Feedier endpoint with its input schema, including the required carrier and recipient fields, so the agent calls the right endpoint without browsing the docs.

## Related APIs

- **Typeform** — Conversational survey builder with strong consumer-facing UX
- **SurveyMonkey** — Mature general-purpose survey platform with broad question library
- **Qualtrics** — Enterprise experience management platform with deep analytics

## FAQ

### Why is there no official OpenAPI spec for Feedier API?

Feedier documents its API on Apiary but does not publish a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Feedier API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Feedier API use?

Feedier uses bearer tokens issued from the workspace settings. Through Jentic the bearer is stored in the vault and injected into the Authorization header at call time so the raw token never enters agent context.

### Can I send a Feedier survey via SMS?

Yes. POST `/push/sms` sends a survey link by SMS to the supplied phone number using the specified carrier ID, and POST `/push/email` is the email equivalent.

### What are the rate limits for the Feedier API?

Feedier does not publish numeric rate limits in this spec; quotas are tied to the workspace plan. Apply backoff on 429 responses and consult your Feedier dashboard for any plan-specific throughput caps.

### How do I send a Feedier email survey through Jentic?

Run pip install jentic, search 'send a feedier email survey', load POST `/push/email`, and execute it with the recipient email and carrier ID to dispatch the survey.

### Can I retrieve testimonials for use on my website?

Yes. GET /testimonials returns the approved testimonials for the account, suitable for piping into a marketing CMS or static site build.

### Can I limit what my agent is allowed to do with the Feedier API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Feedier operations and credentials the agent may use. You can allow it to only push surveys through POST `/push/email` and POST `/push/sms` and read responses through GET /feedbacks, while withholding the rest. A write such as updating a reward transaction through POST `/feedbacks/reward/transaction` is available to the agent only when you explicitly add it.