Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wispr AI User Management API

The User Management API from Wispr AI — 17 operation(s) for user management.

Wispr AI User Management API is one of 50 APIs that Wispr AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User Management. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 23 operations across 17 paths, and defines 20 schemas. It is described by OpenAPI 3.0.3, at version 0.5.2.

Requests are made against the base URL https://api.wisprflow.ai.

23 operations 17 paths 20 schemas 3 DELETE10 GET9 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.5.2
Base URL
https://api.wisprflow.ai
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Wispr AI User Management API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (ApiKeyHeaderPatched). An API key is passed in the header as X-API-Key (APIKeyHeader).

Paths & Operations 23

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

User Management 23
GET
/api/v1/user/profile
Get User Profile
get_user_profile → 200
PUT
/api/v1/user/profile
Update User Profile
update_user_profile body → 200422
GET
/api/v1/user/user-id
Get User Id
get_user_id → 200
GET
/api/v1/user/preferences
Get User Preference
get_user_preference → 200
POST
/api/v1/user/preferences
Update User Preference
update_user_preference body → 200422
POST
/api/v1/user/onboarding-answers
Save Onboarding Answers
save_onboarding_answers body → 200422
GET
/api/v1/user/dictionary
Get User Dictionary
get_user_dictionary → 200
POST
/api/v1/user/dictionary
Update User Dictionary
update_user_dictionary body → 200422
DELETE
/api/v1/user/dictionary
Delete User Dictionary
delete_user_dictionary → 200
DELETE
/api/v1/user/dictionary/{word_id}
Delete Word In Dictionary
delete_word_in_dictionary 1 param → 200422
GET
/api/v1/user/student_status
Get Student Status
get_student_status → 200
POST
/api/v1/user/update_student_status
Update Student Status
update_student_status body → 200422
POST
/api/v1/user/onboarding_complete
Onboarding Complete
onboarding_complete 8 params → 200422
POST
/api/v1/user/claim_trial_extension
Claim Trial Extension
claim_trial_extension → 200
GET
/api/v1/user/user_stats
Get User Stats
get_user_stats → 200
GET
/api/v1/user/hipaa-baa
Get Hipaa Baa Status
get_hipaa_baa_status → 200
POST
/api/v1/user/hipaa-baa
Sign Hipaa Baa
sign_hipaa_baa body → 200422
DELETE
/api/v1/user/hipaa-baa
Revoke Hipaa Baa
revoke_hipaa_baa → 200
POST
/api/v1/user/request_push_notification
Request Push Notification
request_push_notification body → 200422
POST
/api/v1/user/register_device
Register Device
register_device body → 200422
GET
/api/v1/user/registered_devices
Get Registered Devices
get_registered_devices → 200
GET
/api/v1/user/export_data
Export User Data
export_user_data 1 param → 200422
GET
/api/v1/user/trial_status
Get Trial Status
get_trial_status → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are DictionaryItemOld (12 properties), UserPreferencesUpdate (12 properties), RegisterDeviceRequest (10 properties), PersonalizationStyles (5 properties). Each schema is shown below with its type and property counts.

RegisterDeviceRequest
object
10 properties 6 required
OnboardingAnswersResponse
object
Acknowledgement response after onboarding answers are submitted.
1 property 1 required
DictionaryItemOld
object
12 properties 7 required
PolishInstructions
object
Saved toggle rules for Polish transforms (built-in defaults + custom).
2 properties
UserProfileResponse
object
4 properties
SubmitOnboardingAnswersRequest
object
Request body carrying the user's onboarding answers and fulfilled intents.
2 properties 1 required
HTTPValidationError
object
1 property
UserPreferencesUpdate
object
Model for partial updates to user preferences. All fields are optional but when present must follow the same validation rules as UserPreferences.
12 properties
PersonalizationStyles
object
5 properties
Body_update_student_status_api_v1_user_update_student_status_post
object
3 properties 2 required
TrialVariant
string
Body_request_push_notification_api_v1_user_request_push_notification_post
object
2 properties 2 required
UserProfile
object
Model for user profile information. Kept this seperated from UserPreference in case we have more user profile related fields in the future.
2 properties
ValidationError
object
5 properties 3 required
DeviceInfoStatus
string
NotetakerTranscriptRetention
string
OnboardingIntent
string
UserPreference
object
2 properties 1 required
SignHipaaBaaRequest
object
1 property 1 required
PersonalizationStyle
string
Represents the style for personalization settings.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wispr-ai-user-management-api-openapi.yml Raw ↑

Other APIs Wispr AI publishes across the network.

Wispr AI Analytics API
Wispr AI Analytics Registry API
Wispr AI Attribution Tracking API
Wispr AI Authentication API
Wispr AI Automations API
Wispr AI Calendar API
Wispr AI Connectors API
Wispr AI Cost Centers API
Wispr AI Dash API
Wispr AI Dictionary API
Wispr AI Enterpret API
Wispr AI Enterprise API