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

Hey API Users API

The Users API from Hey API — 6 operation(s) for users.

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

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

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

Requests are made against a single base URL, https://api.heyapi.dev.

10 operations 6 paths 7 schemas 2 DELETE4 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.heyapi.dev
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Hey API Users API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (ApiKey). It accepts HTTP bearer tokens (JWT) (Clerk).

  • ApiKey — API key
  • Clerk — Clerk JWT token

Paths & Operations 10

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

Users 10
GET
/v1/users/me
→ 200401
GET
/v1/users/{user_id}/api-keys
4 params → 200401
POST
/v1/users/{user_id}/api-keys
1 param → 200401403
DELETE
/v1/users/{user_id}/api-keys/{api_key_id}
2 params → 200401403
POST
/v1/users/{user_id}/api-keys/{api_key_id}
2 params → 200401403
GET
/v1/users/{user_id}/roles
4 params → 200401
GET
/v1/users/{user_id}/waitlists
4 params → 200401
POST
/v1/users/{user_id}/waitlists
1 param body → 200401403
DELETE
/v1/users/{user_id}/waitlists/{waitlist_id}
2 params → 200401403
PUT
/v1/users/{user_id}/waitlists/{waitlist_id}
2 params body → 200401403

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are User (9 properties), Role (6 properties), ApiKeyConcealed (5 properties), Waitlist (5 properties). Each schema is shown below with its type and property counts.

ApiKey
CursorResponse
object
4 properties 4 required
Waitlist
object
5 properties 5 required
User
object
9 properties 8 required
ApiKeyConcealed
object
5 properties 5 required
WaitlistFeature
string
Role
object
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hey-api-users-api-openapi.yml Raw ↑

Other APIs Hey API publishes across the network.

Hey API Openapi-Ts
Hey API Get API
Hey API Hey API API
Hey API Internal API
Hey API Organizations API
Hey API Specifications API
Where this information came from

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