HEY is automatable through its API

HEY is automatable today through its API at https://app.hey.com. The official SDK default host is that URL. A static token is placed on the Authorization header. The same SDK documents OAuth 2.0 with PKCE, including refresh. hey auth token prints the bearer token, and hey auth login --token stores one without a prompt. The SDK lists boxes, messages, postings, contacts, calendars, search, and journal among the account services. The hey CLI is the documented command client. Piped commands write JSON, and the opened command guide covers mail, search, contacts, calendar, and journal. hey mcp is the official stdio MCP server for boxes, search, threads, contacts, todos, calendars, and identity. It uses the same signed-in credentials. Mutations are not retried automatically. HEY for You is $99 per year after a 30-day trial that does not ask for a credit card. HEY for Domains is $12 per user per month. The service is vendor-hosted. The homepage says it is on the web and on Mac, Windows, Linux, iOS, and Android. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API and the CLI each score 8. The MCP server scores 7 because it is a local subset of that account. The API is the best path because a bearer token or an OAuth client does not require the hey binary or an MCP host. The CLI is how the opened docs print that bearer token.

Best path today: api · Overall automatability: 8/10