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 Share Sensor Type API

The share-sensor-type API from 30MHz — 9 operation(s) for share-sensor-type.

30MHz Share Sensor Type API is one of 127 APIs that 30MHz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include share-sensor-type. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 9 operations across 9 paths, and defines 7 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.

9 operations 9 paths 7 schemas 1 DELETE5 GET3 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 Share Sensor Type API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 9

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

share-sensor-type 9
GET
/share-sensor-type/shared-by/organization/{organizationId}
Returns all sensor types shared by an organization
getSharedByOrganization 1 param → 200403
GET
/share-sensor-type/{sensorTypeId}/shared-with
Get shared information about the sensor type
getSharedSensorTypeSharedWith 1 param → 200403500
POST
/share-sensor-type/sensor-type/{sensorTypeId}/group/{groupId}
Share a sensor type with a group
shareSensorTypeWithGroup 2 params body → 200403500
POST
/share-sensor-type/sensor-type/{sensorTypeId}/organization/{organizationId}
Share a sensor type with an organization
shareSensorTypeWithOrganization 2 params body → 200403500
POST
/share-sensor-type/sensor-type/{sensorTypeId}/user/{email}
Share a sensor type with a user
shareSensorTypeWithUser 2 params body → 200403500
GET
/share-sensor-type/group/{groupId}
Get shared sensor types with a group
sharedSensorTypesWithGroup 1 param → 200403500
GET
/share-sensor-type/organization/{organizationId}
Get shared sensor types with an organization
sharedSensorTypesWithOrganization 1 param → 200403500
GET
/share-sensor-type/user/{email}
Get shared sensor types shared with a user
sharedSensorTypesWithUser 1 param → 200403500
DELETE
/share-sensor-type/{sharedSensorTypeId}
Unshare a sensor type
unshareSensorType 1 param → 200403500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SensorType (32 properties), SharedSensorType (13 properties), SensorTypeEnumDataMapping (3 properties), NotificationTemplate (3 properties). Each schema is shown below with its type and property counts.

NotificationTemplate
object
3 properties
SensorTypeEnumData
object
2 properties
SensorTypeEnumDataMapping
object
3 properties
SharedByUserDetails
object
2 properties
SensorType
object
Authorization entity
32 properties 2 required
SharedWithUserDetails
object
2 properties
SharedSensorType
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

30mhz-share-sensor-type-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 Share Sensor Type 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.