Feedier API

Name: Feedier API API
Brand: Feedier API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms Surveysbearer8 EndpointsREST

For Agents

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

Connect the Feedier API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Feedier API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Feedier API API.

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

GET STARTED

Start building with Feedier API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Feedier API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Feedier API API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault.

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

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for feedier api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Feedier bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped reference and Jentic injects the Authorization header at call time, so raw tokens never enter agent context.

Intent-based discovery

Agents search by intent (e.g. 'send a feedier email survey') and Jentic returns the matching Feedier endpoint with its input schema, including required carrier and recipient fields.

Time to first call

Direct Feedier integration: 1 day for auth, push setup, and feedback polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Typeform

Conversational survey builder with strong consumer-facing UX

Choose Typeform when survey UX and quiz logic matter more than reward and testimonial workflows.

Alternative

SurveyMonkey

Mature general-purpose survey platform with broad question library

Choose SurveyMonkey for large-sample research surveys outside the post-purchase NPS context.

Alternative

Qualtrics

Enterprise experience management platform with deep analytics

Choose Qualtrics for enterprise CX programmes that need governance, advanced statistics, and integrations beyond Feedier's scope.

FAQs

Specific to using Feedier API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.