How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Whisperr, Inc. Users API

The Users API from Whisperr, Inc. — 3 operation(s) for users.

Whisperr, Inc. Users API is one of 7 APIs that Whisperr, Inc. publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, and 3 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.2.0.

Requests are made against a single base URL, https://api.whisperr.net.

3 operations 3 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.2.0
Base URL
https://api.whisperr.net
Authentication
API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Whisperr, Inc. Users API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (APIKey). It accepts HTTP bearer tokens (Supabase JWT) (DashboardBearer). An API key is passed in the header as X-Whisp-Onboarding-Import-Secret (OnboardingImportSecret).

  • APIKey — Use Authorization: Bearer .
  • DashboardBearer — Use Authorization: Bearer from Supabase Auth.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Users 3
POST
/v1/identify
Identify a runtime user
identifyUser body → 200400401
GET
/v1/users/{external_id}
Get a runtime user by external id
getUser 1 param → 200401404
GET
/v1/users/{external_id}/state
Get runtime state for a user
getUserState 1 param → 200401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are IdentifyRequest (4 properties), IngestedUserChannel (4 properties), IdentifyResponse (1 property), ErrorResponse (1 property). Each schema is shown below with its type and property counts.

GetUserStateResponse
object
1 property 1 required
GetUserResponse
object
1 property 1 required
ErrorResponse
object
1 property 1 required
IngestedUserChannel
object
4 properties 2 required
IdentifyRequest
object
4 properties 1 required
IdentifyResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

whisperr-inc-users-api-openapi.yml Raw ↑

Other APIs Whisperr, Inc. publishes across the network.

Whisperr, Inc. Dashboard API
Whisperr, Inc. Decisioning API
Whisperr, Inc. Delivery API
Whisperr, Inc. Ingestion API
Whisperr, Inc. Internal API
Whisperr, Inc. System API
Where this information came from

This is an independent, third-party profile of Whisperr, Inc. Users API, 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.