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 API contracts indexed 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.

The HappyOrNot catalog on APIs.io includes 1 Spectral governance ruleset.

HappyOrNot’s developer surface includes authentication, changelog, documentation, API reference, getting-started guide, support, engineering blog, and 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.2/100 developing ▬ flat Agent 21/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 3 Agent Skills

Company Enterprise Customer Experience Customer Feedback Surveys Analytics Voice of Customer Retail Feedback

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Service Management

BC-430

alert-commentsbutton-feedbackscontact-detailsdemographicsfollow-up-feedbacksfollow-up-options

GET /results/button-feedbacks.{format} GET /results/follow-up-feedbacks.{format} GET /results/text-feedbacks.{format} GET /surveys.{format}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 51.2/100 · developing

Contract Quality 10.5 / 21

Developer Ergonomics 10.0 / 17

Access Clarity 10.7 / 17

Operational Transparency 2.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/happyornot/"><img src="https://apis.io/badge/happyornot/card.svg" alt="HappyOrNot on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 49.6 — up to +12.6 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Operational Transparency scores 26.3 — up to +9.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/happyornot/apis.yml: open an issue on github.com/api-evangelist/happyornot to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Surveys, Market Research and Experience Management	long-tail	2.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

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

Open Collections 21

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

HappyOrNot Customer API v2 alert-comments API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments alert-specifications API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments alerts API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments button-feedbacks API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments contact-details API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments custom-data-fields API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments demographics API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments experience-points API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments follow-up-feedbacks API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments follow-up-option-localizations API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments follow-up-options API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments follow-up-question-localizations API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments follow-up-questions API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments metadata API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments question-localizations API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments questions API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments smileys API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments surveys API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments text-feedbacks API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments token-introspection API

OPEN COLLECTION

HappyOrNot Customer API v2 alert-comments users API

OPEN COLLECTION

Scroll for all 21

Arazzo Workflows 2

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.

ARAZZO

Monitor HappyOrNot alerts

Read alert specifications, poll triggered alerts, then read their comments.

ARAZZO

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Export a full HappyOrNot feedback dataset

AGENT SKILL

Fetch HappyOrNot button feedback for a location

AGENT SKILL

Monitor HappyOrNot alerts

AGENT SKILL

HappyOrNot API pricing

Prices published by HappyOrNot, read 2026-10-28 from www.happy-or-not.com/en/pricing-and-features/.

Plan	Price
Essentials	Get a Quote Includes: Smiley Terminal; continuous high-volume feedback
Professional	Get a Quote Includes: All Smiley products; Analytics and AI open feedback model
Managed	Get a Quote Includes: Professional package plus assigned team of experts

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Happyornot Plans Pricing

3 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

HappyOrNot

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Happyornot Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

HappyOrNot API Rules

61 rules · 54 errors 6 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Happyornot Openapi Overlay

2 actions · update · happyornot-openapi-original.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Happyornot Authentication

apiKey · 2 schemes

SECURITY

Happyornot Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

OpenAPI

OpenAPI

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

AgentSkill

WellKnown

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

Arazzo

Arazzo

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Deprecation

Deprecation

ChangeLog

ChangeLog

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: happyornot
name: HappyOrNot
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/happyornot/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.happy-or-not.com/wp-content/uploads/2021/03/HappyOrNot-logo.png
tags:
- Company
- Enterprise
- Customer Experience
- Customer Feedback
- Surveys
- Analytics
- Voice of Customer
- Retail
- Feedback
apis:
- aid: happyornot:happyornot-alert-comments-api
  name: HappyOrNot Alert Comments API
  description: Endpoints and data definitions related to alert comments which have been written for alerts
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - alert-comments
  properties:
  - type: OpenAPI
    url: openapi/happyornot-alert-comments-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-alert-specifications-api
  name: HappyOrNot Alert Specifications API
  description: Endpoints and data definitions related to alert specifications based on which alerts are triggered
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - alert-specifications
  properties:
  - type: OpenAPI
    url: openapi/happyornot-alert-specifications-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-alerts-api
  name: HappyOrNot Alerts API
  description: Endpoints and data definitions related to alerts which have been triggered by incoming feedback, based on alert
    specfications
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Alerts
  tags_raw:
  - alerts
  properties:
  - type: OpenAPI
    url: openapi/happyornot-alerts-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-button-feedbacks-api
  name: HappyOrNot Button Feedbacks API
  description: Button feedback related endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - button-feedbacks
  properties:
  - type: OpenAPI
    url: openapi/happyornot-button-feedbacks-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-contact-details-api
  name: HappyOrNot Contact Details API
  description: Contact details data endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Contact Details
  tags_raw:
  - contact-details
  properties:
  - type: OpenAPI
    url: openapi/happyornot-contact-details-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-custom-data-fields-api
  name: HappyOrNot Custom Data Fields API
  description: Endpoints and data definitions related to custom data fields
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Custom Data Fields
  tags_raw:
  - custom-data-fields
  properties:
  - type: OpenAPI
    url: openapi/happyornot-custom-data-fields-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-demographics-api
  name: HappyOrNot Demographics API
  description: Demographics data endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Demographics
  tags_raw:
  - demographics
  properties:
  - type: OpenAPI
    url: openapi/happyornot-demographics-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-experience-points-api
  name: HappyOrNot Experience Points API
  description: Experience points and groups related endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - experience-points
  properties:
  - type: OpenAPI
    url: openapi/happyornot-experience-points-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-follow-up-feedbacks-api
  name: HappyOrNot Follow Up Feedbacks API
  description: Follow-up feedback related endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - follow-up-feedbacks
  properties:
  - type: OpenAPI
    url: openapi/happyornot-follow-up-feedbacks-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-follow-up-option-localizations-api
  name: HappyOrNot Follow Up Option Localizations API
  description: Endpoints and data definitions related to localizations for selectable options for follow ups in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - follow-up-option-localizations
  properties:
  - type: OpenAPI
    url: openapi/happyornot-follow-up-option-localizations-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-follow-up-options-api
  name: HappyOrNot Follow Up Options API
  description: Endpoints and data definitions related to selectable options for follow ups in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - follow-up-options
  properties:
  - type: OpenAPI
    url: openapi/happyornot-follow-up-options-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-follow-up-question-localizations-api
  name: HappyOrNot Follow Up Question Localizations API
  description: Endpoints and data definitions related to localizations for questions used for follow ups in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - follow-up-question-localizations
  properties:
  - type: OpenAPI
    url: openapi/happyornot-follow-up-question-localizations-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-follow-up-questions-api
  name: HappyOrNot Follow Up Questions API
  description: Endpoints and data definitions related to questions used for follow ups in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - follow-up-questions
  properties:
  - type: OpenAPI
    url: openapi/happyornot-follow-up-questions-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-metadata-api
  name: HappyOrNot Metadata API
  description: Metadata related endpoints and daa definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Metadata
  tags_raw:
  - metadata
  properties:
  - type: OpenAPI
    url: openapi/happyornot-metadata-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-question-localizations-api
  name: HappyOrNot Question Localizations API
  description: Endpoints and data definitions related to localizations for question used in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - question-localizations
  properties:
  - type: OpenAPI
    url: openapi/happyornot-question-localizations-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-questions-api
  name: HappyOrNot Questions API
  description: Endpoints and data definitions related to questions used in surveys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Questions
  tags_raw:
  - questions
  properties:
  - type: OpenAPI
    url: openapi/happyornot-questions-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-smileys-api
  name: HappyOrNot Smileys API
  description: Endpoints and data definitions related to smileys
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - smileys
  properties:
  - type: OpenAPI
    url: openapi/happyornot-smileys-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-surveys-api
  name: HappyOrNot Surveys API
  description: Surveys related endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Surveys
  tags_raw:
  - surveys
  properties:
  - type: OpenAPI
    url: openapi/happyornot-surveys-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-text-feedbacks-api
  name: HappyOrNot Text Feedbacks API
  description: Text feedback related endpoints and data definitions
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - text-feedbacks
  properties:
  - type: OpenAPI
    url: openapi/happyornot-text-feedbacks-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-token-introspection-api
  name: HappyOrNot Token Introspection API
  description: Token introspection including token scopes
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - Token Introspection
  tags_raw:
  - token-introspection
  properties:
  - type: OpenAPI
    url: openapi/happyornot-token-introspection-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
- aid: happyornot:happyornot-users-api
  name: HappyOrNot Users API
  description: Endpoints and data definitions related to users
  humanURL: https://api.happy-or-not.com/v2/
  baseURL: https://api.happy-or-not.com/v2/
  tags:
  - User
  tags_raw:
  - users
  properties:
  - type: OpenAPI
    url: openapi/happyornot-users-api-openapi.yml
  - type: Documentation
    url: https://happyornot.github.io/docs/
  - type: APIReference
    url: https://api.happy-or-not.com/v2/
  - type: Authentication
    url: authentication/happyornot-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/happyornot-plans-pricing.yml
- type: CapabilityMap
  url: capabilities/happyornot-capability-edges.yml
  name: HappyOrNot Business Capability Map
- type: OpenAPI
  url: openapi/_original/happyornot-openapi-original.yml
- type: Overlay
  url: overlays/happyornot-openapi-overlay.yaml
- type: Authentication
  url: authentication/happyornot-authentication.yml
- type: DomainSecurity
  url: security/happyornot-domain-security.yml
- type: Conventions
  url: conventions/happyornot-conventions.yml
- type: ErrorCatalog
  url: errors/happyornot-problem-types.yml
- type: Lifecycle
  url: lifecycle/happyornot-lifecycle.yml
- type: Deprecation
  url: https://happyornot.github.io/docs/api-v1/
- type: ChangeLog
  url: changelog/happyornot-changelog.yml
- type: DataModel
  url: data-model/happyornot-data-model.yml
- type: Conformance
  url: conformance/happyornot-conformance.yml
- type: X-MCPServerCandidate
  url: mcp/happyornot-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Packages
  url: packages/happyornot-packages.yml
- type: LLMsTxt
  url: llms/happyornot-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Resolve an experience point and fetch its button feedback
  url: arazzo/happyornot-fetch-feedback.yml
- type: Arazzo
  name: Monitor HappyOrNot alerts
  url: arazzo/happyornot-monitor-alerts.yml
- type: WellKnown
  url: well-known/happyornot-well-known.yml
- type: DeveloperPortal
  url: https://happyornot.github.io/docs/
- type: Documentation
  url: https://happyornot.github.io/docs/
- type: APIReference
  url: https://api.happy-or-not.com/v2/
- type: GettingStarted
  url: https://happyornot.github.io/docs/
- type: Support
  url: https://support.happy-or-not.com/
- type: Blog
  url: https://www.happy-or-not.com/en/resources/blog/
- type: GitHubOrganization
  url: https://github.com/happyornot
- type: Pricing
  url: https://www.happy-or-not.com/en/pricing/
- type: SignUp
  url: https://reporting.happy-or-not.com/
- type: TermsOfService
  url: https://www.happy-or-not.com/en/terms/
- type: PrivacyPolicy
  url: https://www.happy-or-not.com/en/privacy-policy/
- type: Website
  url: https://www.happy-or-not.com
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

HappyOrNot API — frequently asked questions

Does HappyOrNot have an API?

Yes. APIs.io lists 21 APIs from HappyOrNot, including HappyOrNot Alert Comments API, HappyOrNot Alert Specifications API and HappyOrNot Alerts API, and 18 more.

Is there an OpenAPI specification for the HappyOrNot API?

Yes. APIs.io indexes 21 OpenAPI specifications for HappyOrNot, each linked for download from this page.

How do I authenticate with the HappyOrNot API?

HappyOrNot uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Happyornot Authentication.

How much does the HappyOrNot API cost?

HappyOrNot publishes its prices; its Essentials plan is Get a Quote as of 2026-10-28. APIs.io lists 3 pricing plans for HappyOrNot, with each plan's price, limits and inclusions under Pricing on this page.

Is the HappyOrNot API ready for AI agents?

HappyOrNot has a Kin Score of 51.2 out of 100 (developing) and an Agent Readiness score of 20.9 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/happyornot"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/happyornot/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/happyornot/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.