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

30MHz User API

The user API from 30MHz — 18 operation(s) for user.

30MHz User API is one of 127 APIs that 30MHz 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 a getting-started guide.

This API exposes 19 operations across 18 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.30mhz.com/api.

19 operations 18 paths 9 schemas 3 DELETE8 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.30mhz.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

30MHz User API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 19

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

User 19
GET
/user
Returns the stored information associated to the current user
getUser → 200401404500
POST
/user/sign-up
Sign up
signUp body → 200400403404500
POST
/user/change-password/{email}/{authorizationCode}
Confirms the user's password change
changePassword 2 params body → 200400401500
GET
/user/all
Returns all the system users. Operation reserved to system admins
getAllUsers → 200401500
POST
/user/register/user/{email}
Registers a new guest user that does not belong to any organization.
registerUser 2 params body → 200
POST
/user/activate/user/{email}deprecated
Activates a new user that was added as member of an organization.Authorization…
activateUser 2 params body → 200
GET
/user/account-managers
Returns all the account managers
getAllAccountManagers → 200401500
GET
/user/organization-member/organization/{organizationId}
Returns the organization memberships that belong to an organization
getOrganizationMemberships 1 param → 200401404
GET
/user/organization/{organizationId}
Returns the users that belong to an organization
getOrganizationUsers 1 param → 200401500
GET
/user/{email}
Returns the requested User
getUserByEmail 1 param → 200401403404
DELETE
/user/{email}
Removes the user, along with all her notification settings of checks (follows).
removeUser 1 param → 200401404
GET
/user/has-api-key
Checks if user has an api key
hasAPIKey → 200401
POST
/user/invite/organization/{organizationId}/role/{role}
Invites valid users to join Zensie
invite 3 params body → 200201401404409500
POST
/user/invite
Invites a user to an organization
inviteUser body → 200201400401403409500
POST
/user/api-key/request
Requests an API key for the authenticated user.
requestAPIKey → 201
POST
/user/api-key/request-with-password
Requests an API key for a user with valid username and password.
requestAPIKeyWithUsernameAndPassword body → 200
GET
/user/change-password/{email}
Request to make a password change for the user with given email
requestChangePassword 1 param → 200400500
DELETE
/user/api-key
Revokes the current API key for the authenticated user
revokeAPIKey → 200401
DELETE
/user/{email}/api-key
Revokes the current API key for the user with the given email address
revokeAPIKeyForUser 1 param → 200401

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are User (14 properties), UserInviteRequest (14 properties), UserNew (11 properties), OrganizationMembership (6 properties). Each schema is shown below with its type and property counts.

User
object
A person who uses the platform
14 properties 1 required
UserToken
object
1 property
WebPageReference
object
A reference to a web page
2 properties
UserCredentialsAsGuest
object
Object holding the required properties to register a guest
5 properties
SignUpRequest
object
Payload submitted by an invited user to sign up.
3 properties 2 required
UserNew
object
Object holding the required properties to create a new user
11 properties 3 required
OrganizationMembership
object
A user being a member of an organization with a given role.
6 properties 1 required
Credential
object
Object holding user's credentials
3 properties
UserInviteRequest
object
User Invite to an organization
14 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

30mhz-user-api-openapi.yml Raw ↑

Other APIs 30MHz publishes across the network.

30MHz Admin API
30MHz Agent API
30MHz App API
30MHz App Cultiwatch API
30MHz App Installation Update API
30MHz App Irrigation API
30MHz App Update API
30MHz Assembly API
30MHz Assembly Update API
30MHz Authorization API
30MHz Billing History API
30MHz Billing History Details API
Where this information came from

This is an independent, third-party profile of 30MHz User 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.