30MHz Notification Topic Follow Update API

The notification-topic-follow-update API from 30MHz — 1 operation(s) for notification-topic-follow-update.

Operations 1

POST /notification-topic-follow-update/{notificationTopicId}/user/{email}/organization/{organizationId} Update an existing notification topic follow #

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-follow-update-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.

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

OpenAPI Specification

30mhz-notification-topic-follow-update-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: '2.0'
  title: ZENSIE Notification Topic Follow Update API
servers:
- url: https://api.30mhz.com/api
tags:
- name: notification-topic-follow-update
paths:
  /notification-topic-follow-update/{notificationTopicId}/user/{email}/organization/{organizationId}:
    post:
      tags:
      - notification-topic-follow-update
      summary: Update an existing notification topic follow
      description: Only organization members and administrators of ZENSIE are authorised to call this operation.
      operationId: updateNotificationTopicFollow
      parameters:
      - name: notificationTopicId
        in: path
        required: true
        schema:
          type: string
      - name: email
        in: path
        required: true
        schema:
          type: string
      - name: organizationId
        in: path
        required: true
        schema:
          type: string
      security:
      - Bearer: []
      responses:
        '201':
          description: Notification topic follow update
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationTopicFollow'
            application/zensie-v2+json:
              schema:
                $ref: '#/components/schemas/NotificationTopicFollow'
        '403':
          description: User not allowed to perform the operation
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/NotificationMethods'
components:
  schemas:
    NotificationMethods:
      type: object
      properties:
        methods:
          type: array
          uniqueItems: true
          items:
            type: string
            enum:
            - EMAIL
            - SMS
            - WHATSAPP
    NotificationTopicFollow:
      type: object
      properties:
        email:
          type: string
        methods:
          type: array
          uniqueItems: true
          items:
            type: string
          maxItems: 2147483647
          minItems: 1
        notificationTopicFollowId:
          type: string
        notificationTopicId:
          type: string
        organizationId:
          type: string
      description: Notification topic follow
  securitySchemes:
    Bearer:
      description: ''
      type: apiKey
      name: Authorization
      in: header