30MHz

30MHz Notification Topic API

The notification-topic API from 30MHz — 2 operation(s) for notification-topic.

GitHub OpenAPI

Operations 4

GET /notification-topic Return all the notifications topics #
POST /notification-topic Create a new notification topic #
GET /notification-topic/{notificationTopicId} Retrieve a notification topic with the given id #
DELETE /notification-topic/{notificationTopicId} Delete a notification topic with the given id #

Documentation

📖
Documentation
https://support.30mhz.com/developer-docs
📖
APIReference
https://api.30mhz.com/api/swagger
📖
GettingStarted
https://support.30mhz.com/create-an-api-key

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/30mhz/refs/heads/main/openapi/30mhz-notification-topic-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/30mhz-notification-topic-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

30mhz-notification-topic-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: '2.0'
  title: ZENSIE Notification Topic API
servers:
- url: https://api.30mhz.com/api
tags:
- name: notification-topic
paths:
  /notification-topic:
    get:
      tags:
      - notification-topic
      summary: Return all the notifications topics
      description: Default oauth authentication mechanism required for this operation.
      operationId: getNotificationTopics
      security:
      - Bearer: []
      responses:
        '200':
          description: Returns the list of notification topics
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
            application/zensie-v2+json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
        '401':
          description: Unauthenticated request, cannot perform operation
          content:
            application/json:
              schema:
                type: string
            application/zensie-v2+json:
              schema:
                type: string
        '403':
          description: User not allowed to perform the operation
    post:
      tags:
      - notification-topic
      summary: Create a new notification topic
      description: Only administrators of ZENSIE are authorised to call this operation.
      operationId: createNotificationTopic
      security:
      - Bearer: []
      responses:
        '201':
          description: New notification topic created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
            application/zensie-v2+json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
        '401':
          description: Unauthenticated request, cannot perform operation
          content:
            application/json:
              schema:
                type: string
            application/zensie-v2+json:
              schema:
                type: string
        '403':
          description: User not allowed to perform the operation
        '409':
          description: A notification topic with the given id already exists
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/NewNotificationTopic'
  /notification-topic/{notificationTopicId}:
    get:
      tags:
      - notification-topic
      summary: Retrieve a notification topic with the given id
      description: Default oauth authentication mechanism required for this operation.
      operationId: getNotificationTopic
      parameters:
      - name: notificationTopicId
        in: path
        required: true
        schema:
          type: string
      security:
      - Bearer: []
      responses:
        '200':
          description: Notification topic
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
            application/zensie-v2+json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
        '401':
          description: Unauthenticated request, cannot perform operation
          content:
            application/json:
              schema:
                type: string
            application/zensie-v2+json:
              schema:
                type: string
        '403':
          description: User not allowed to perform the operation
    delete:
      tags:
      - notification-topic
      summary: Delete a notification topic with the given id
      description: Only administrators of ZENSIE are authorised to call this operation.
      operationId: deleteNotificationTopic
      parameters:
      - name: notificationTopicId
        in: path
        required: true
        schema:
          type: string
      security:
      - Bearer: []
      responses:
        '200':
          description: Notification deleted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
            application/zensie-v2+json:
              schema:
                $ref: '#/components/schemas/NotificationTopic'
        '401':
          description: Unauthenticated request, cannot perform operation
          content:
            application/json:
              schema:
                type: string
            application/zensie-v2+json:
              schema:
                type: string
        '403':
          description: User not allowed to perform the operation
components:
  schemas:
    NewNotificationTopic:
      type: object
      properties:
        conditionDescription:
          type: string
        description:
          type: string
        notificationTopicId:
          type: string
    NotificationTopic:
      type: object
      properties:
        conditionDescription:
          type: string
        description:
          type: string
        notificationTopicId:
          type: string
      description: Notification topic
  securitySchemes:
    Bearer:
      description: ''
      type: apiKey
      name: Authorization
      in: header