HappyOrNot
HappyOrNot is a Finnish customer-experience feedback company known for its Smiley Terminal, Smiley Touch and Smiley Digital feedback devices used across retail, airports, healthcare, public sector and workplaces. Its read-only Customer API v2 lets applications and BI tools pull raw feedback data — button (smiley/NPS) ratings, follow-up selections, freeform text, AI demographics, contact-request details and metadata — together with the experience points, groups, surveys, questions, smileys, users and alerts that produce it. Authentication is a package-scoped API token (X-HON-API-Token header or auth query parameter); responses are JSON or CSV, paged with offset/limit and an X-More-Available header. The API is documented with an OpenAPI 3.1 specification and integrates with Power BI, Tableau, Salesforce, Medallia, Qualtrics and Zapier.
HappyOrNot publishes 21 APIs on the APIs.io network, including alert-comments API, alert-specifications API, alerts API, and 18 more. Tagged areas include Company, Enterprise, Customer Experience, Customer Feedback, and Surveys.
HappyOrNot’s developer surface includes authentication, changelog, documentation, API reference, getting-started guide, support, engineering blog, and 23 more developer resources.
Kin Score
APIs 21
Individual APIs this provider publishes, each with its own machine-readable definition.
HappyOrNot alert-comments API
Endpoints and data definitions related to alert comments which have been written for alerts
HappyOrNot alert-specifications API
Endpoints and data definitions related to alert specifications based on which alerts are triggered
HappyOrNot alerts API
Endpoints and data definitions related to alerts which have been triggered by incoming feedback, based on alert specfications
HappyOrNot button-feedbacks API
Button feedback related endpoints and data definitions
HappyOrNot contact-details API
Contact details data endpoints and data definitions
HappyOrNot custom-data-fields API
Endpoints and data definitions related to custom data fields
HappyOrNot demographics API
Demographics data endpoints and data definitions
HappyOrNot experience-points API
Experience points and groups related endpoints and data definitions
HappyOrNot follow-up-feedbacks API
Follow-up feedback related endpoints and data definitions
HappyOrNot follow-up-option-localizations API
Endpoints and data definitions related to localizations for selectable options for follow ups in surveys
HappyOrNot follow-up-options API
Endpoints and data definitions related to selectable options for follow ups in surveys
HappyOrNot follow-up-question-localizations API
Endpoints and data definitions related to localizations for questions used for follow ups in surveys
HappyOrNot follow-up-questions API
Endpoints and data definitions related to questions used for follow ups in surveys
HappyOrNot metadata API
Metadata related endpoints and daa definitions
HappyOrNot question-localizations API
Endpoints and data definitions related to localizations for question used in surveys
HappyOrNot questions API
Endpoints and data definitions related to questions used in surveys
HappyOrNot smileys API
Endpoints and data definitions related to smileys
HappyOrNot surveys API
Surveys related endpoints and data definitions
HappyOrNot text-feedbacks API
Text feedback related endpoints and data definitions
HappyOrNot token-introspection API
Token introspection including token scopes
HappyOrNot users API
Endpoints and data definitions related to users
Scroll for all 21
Arazzo Workflows 3
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOResolve an experience point and fetch its button feedback
Walk the experience-point tree, resolve surveys, then pull button feedback for a period.
ARAZZOMonitor HappyOrNot alerts
Read alert specifications, poll triggered alerts, then read their comments.
ARAZZOMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
happyornot-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type