Synadia Communications NATS Core Messaging (Experimental) API

The NATS Core Messaging (Experimental) API from Synadia Communications — 1 operation(s) for nats core messaging (experimental).

Operations 3

POST /nats/subjects/{subject} Makes a request #
PUT /nats/subjects/{subject} Publishes a message with an optional reply #
GET /nats/subjects/{subject} Creates a subscription #

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/synadia-communications-nats-core-messaging-experimental-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

synadia-communications-nats-core-messaging-experimental-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: NATS HTTP Gateway NATS Core Messaging (Experimental) API
  description: 'This is the API for interacting with NATS and NATS

    based services using HTTP.'
  version: 1.0.0
servers:
- url: https://api.ngs.global/v1
security:
- ApiKeyAuth: []
tags:
- name: NATS Core Messaging (Experimental)
paths:
  /nats/subjects/{subject}:
    parameters:
    - name: subject
      in: path
      description: subject
      required: true
      style: simple
      explode: false
      schema:
        maximum: 1
        minimum: 1
        type: string
    - in: query
      name: timeout
      required: false
      description: how long to wait for a response in milliseconds. Default is 2000 milliseconds.
      schema:
        type: number
        format: uint64
    - name: NatsH-*
      in: header
      required: false
      explode: true
      pattern: ^NatsH-*
      description: Header prefix - any HTTP request with a header that has the `NatsH-` prefix will have the prefix dropped, and have the header included on the published message.
      schema:
        type: string
    post:
      tags:
      - NATS Core Messaging (Experimental)
      summary: Makes a request
      operationId: request
      requestBody:
        content:
          application/octet-stream:
            schema:
              type: string
              format: binary
          application/text:
            schema:
              type: string
          application/json:
            schema:
              type: object
              additionalProperties:
                type: object
      responses:
        '200':
          description: Success response
          content:
            application/json:
              schema:
                type: object
                properties:
                  subject:
                    type: string
                  reply:
                    type: string
                  data:
                    type: string
                    format: binary
                  headers:
                    type: object
                    additionalProperties:
                      type: string
                    x-schema-name: Header
                example:
                  headers:
                    key: headers
                  data: ''
                  subject: subject
                  reply: reply
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
    put:
      tags:
      - NATS Core Messaging (Experimental)
      summary: Publishes a message with an optional reply
      operationId: publish
      parameters:
      - name: reply
        in: query
        description: subject
        required: true
        explode: false
        schema:
          maximum: 1
          minimum: 1
          type: string
      - name: NatsH-*
        in: header
        required: false
        explode: true
        pattern: ^NatsH-*
        description: Header prefix - any HTTP request with a header that has the `NatsH-` prefix will have the prefix dropped, and have the header included on the published message.
        schema:
          type: string
      - name: query
        in: query
        description: queue group for the subscription
        required: false
        explode: false
        schema:
          maximum: 1
          minimum: 1
          type: string
      requestBody:
        content:
          application/octet-stream:
            schema:
              type: string
              format: binary
          application/text:
            schema:
              type: string
          application/json:
            schema:
              type: object
              additionalProperties:
                type: object
      responses:
        '200':
          description: Success response
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
    get:
      tags:
      - NATS Core Messaging (Experimental)
      summary: Creates a subscription
      operationId: subscribe
      parameters:
      - name: limit
        in: query
        description: the maximum number of keys to return, note internally it is limited to 1000
        required: false
        style: form
        explode: true
        schema:
          type: number
          default: 1000
          maximum: 1000
          minimum: 1
      responses:
        '200':
          description: Success response
          content:
            text/event-stream:
              schema:
                type: object
                properties:
                  subject:
                    type: string
                  reply:
                    type: string
                  data:
                    type: string
                    format: binary
                  headers:
                    type: object
                    additionalProperties:
                      type: string
                    x-schema-name: Header
                example:
                  headers:
                    key: headers
                  data: ''
                  subject: subject
                  reply: reply
        '400':
          description: Invalid request
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      name: Authorization
      in: header