Hiya
Hiya is an AI-native voice security company that blocks spam, fraud, and deepfake calls at network scale for mobile operators, enterprises, and consumers. Its developer platform exposes several REST APIs: Hiya Connect for branded outbound calling (registering originating numbers, managing branded phone numbers, logos, and managed brands), Hiya Protect for spam and scam reputation (business partner reputation submission, spammer and profile-phone caches, and voice scam protection reporting), Hiya Audio Intelligence for audio-based authenticity, identity, and voiceprint verification (deepfake and synthetic-voice detection), and the Hiya AI Voice Platform for call logs, contacts, relations, notifications, and an AI voice assistant. APIs are served over HTTPS from api.hiya.com with HTTP Basic authentication using an App ID and App Secret (bearer tokens for Audio Intelligence), plus iOS and Android mobile SDKs for embedding caller ID and protection in apps.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Hiya the way a machine reads it — 6 machine-readable artifacts across 4 APIs, 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 — Hiya scores 30.0/100 (thin), with a separate agent-readiness read of 10/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hiya
Each block below is one kind of artifact we hold for Hiya. 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 4
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.
Hiya Connect API
Branded calling API to register outbound originating numbers, manage Connect phone numbers and managed brands, upload and manage brand logos, and read branded-phones cache and b...
Hiya Protect API
Spam and scam protection API covering the business partner reputation surface (register businesses and phones, query reputation), spammer and profile-phone caches distributed as...
Hiya Audio Intelligence API
Audio-based authenticity, identity, and voiceprint verification API for detecting deepfakes and synthetic voices, managing audios, identities, identity/message/authenticity veri...
Hiya AI Voice Platform API
AI voice assistant and call management API for call logs, contacts, relations, user accounts and preferences, notification tokens, call feedback, assistant voices, number profil...
Security 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 Hiya — 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 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
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 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hiya · machine-readable index on apis.io