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.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles HappyOrNot the way a machine reads it — 47 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HappyOrNot scores 43.4/100 (developing), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from HappyOrNot's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/happyornot/"
title="HappyOrNot on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/happyornot.svg"
alt="HappyOrNot Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/happyornot/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/happyornot/"
title="HappyOrNot on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/happyornot/card.svg"
alt="HappyOrNot Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile HappyOrNot
Each block below is one kind of artifact we hold for HappyOrNot. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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 within the panel for all 21 ·
Open Collections 22
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments alerts API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments demographics API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments metadata API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments questions API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments smileys API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments surveys API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments text-feedbacks API
OPEN COLLECTIONHappyOrNot Customer API v2 alert-comments users API
OPEN COLLECTIONScroll within the panel for all 22 ·
Arazzo Workflows 2
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Resolve 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.
ARAZZOSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for HappyOrNot — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
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 within the panel 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 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/happyornot · machine-readable index on apis.io
This is an independent, third-party profile of HappyOrNot, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.