Happy Hear Audio

Developers

Build on Happy Hear Audio

Happy Hear Audio exposes an operator’s account two ways: to AI assistants and other MCP clients through one remote server, and to scripts and integrations through a read-only HTTP API with API keys. Both run the same operations, so this section documents them once: the server URL and how a client gets a token, every action with its parameters and an example call, the limits, the errors, and the HTTP endpoints. Everything here is generated from the server’s own registrations, so it cannot describe something the server does not do.

Connector

Server URL, OAuth 2.1 with dynamic client registration, request and response shapes.

Actions

One page per action: parameters, example call, example result, errors.

Limits

Per-minute request limit, daily write caps, and what is never exposed.

Errors

HTTP-level refusals and tool-level failures, with what to do about each.

Changelog

Dated changes to the connector, newest first.

API

The read-only HTTP API: who can use it, API keys, the Authorization header, limits, versioning.

API reference

Every endpoint with its parameters, an example request and response, and the error codes, from the OpenAPI document.

At a glance

  • Protocol: Model Context Protocol over Streamable HTTP, stateless JSON. Server URL https://www.happyhearaudio.com/api/mcp.
  • Authentication: OAuth 2.1 authorization code with PKCE. Dynamic Client Registration is on, so a client needs no pre-shared credentials.
  • Actions: 10 in all, 7 read-only and 3 that write. Every write is logged and has a daily cap.
  • Scope: the signed-in operator’s own account. Guest audio, transcripts, phone numbers, speaker names and passwords are never returned.
  • Availability: every plan, including the free first event. No extra charge for the connector itself.

Machine-readable description

A JSON description of the server, its authorization endpoints, its limits and every action’s input schema is published at /developers/connector/tools.json. The tool entries are the same shapes a client receives from tools/list after connecting, so you can read the connector, or generate types from it, without an account.

bash
curl https://www.happyhearaudio.com/developers/connector/tools.json

Is there a REST API?

Yes, since October 2026, and read-only to start. Operators on the Monthly plan create an API key in Settings and call the same seven read operations over plain HTTPS: HTTP API covers keys, the header, limits and versioning, and the API reference lists every endpoint. The machine-readable description is /api/v1/openapi.json. Writes and webhooks are not in it yet; if you need them, email hello@happyhearaudio.com and describe the integration.

Not a developer?

Operators do not need any of this. The setup guide at Connect an AI assistant walks through adding Happy Hear Audio to Claude or ChatGPT in a few clicks, and AI assistant actions describes the same ten actions in plain words.