Skip to main content

Public Channels

Pushmark currently centers its API flow around public channels.

How they work​

  • You create a channel in the dashboard.
  • Subscribers join that channel from the Pushmark app by scanning its QR code or opening the join link.
  • Your automation sends notifications by posting JSON to that channel's hash URL.

A public channel is a good fit for:

  • team deployment updates
  • shared operational alerts
  • community or project notifications
  • local automation that should reach more than one subscriber

Sending into a public channel​

The request target is the channel hash itself:

POST https://api.pushmark.app/<channel_hash>

The payload shape is intentionally small:

{
  "message": "Deploy finished successfully.",
  "type": "success"
}

Channel hash​

You can think of the channel hash as the address of that notification stream.

  • Keep it available to the systems that need to send notifications.
  • Rotate to a new channel if you need to change distribution or reset a shared workflow.
  • Use separate channels for different audiences and urgency levels.

Private channels​

Private channels are coming soon.

The product UI already points to a private-channel path, but the current docs should assume:

  • public channels are the supported delivery model today
  • private channels are not yet part of the stable self-serve setup