Pushinator API

Use the Pushinator API via direct

curl

calls to

send push notifications

to mobile devices.

Official docs:

https://pushinator.com/api

When to Use

Use this skill when you need to:

Send push notifications

to mobile devices

Alert users

about events, deployments, or updates

Integrate notifications

into CI/CD pipelines

Notify yourself

when long-running tasks complete

Prerequisites

Sign up at

Pushinator

Download the Pushinator app on your mobile device

Create a channel in the

Console

Generate an API token at

Tokens

Store credentials in environment variables

export

PUSHINATOR_TOKEN

=

"your-api-token"

Pricing

Free

3 devices, 200 notifications/month

Pro

($9.99/mo): 20 devices, 2,000 notifications/month

Scale

($29.99/mo): 50 devices, 20,000 notifications/month

Important:

When using

$VAR

in a command that pipes to another command, wrap the command containing

$VAR

in

bash -c '...'

. Due to a Claude Code bug, environment variables are silently cleared when pipes are used directly.

bash

-c

'curl -s "https://api.example.com" -H "Authorization: Bearer $API_KEY"'

How to Use

Base URL:

https://api.pushinator.com

Required headers:

Authorization: Bearer ${PUSHINATOR_TOKEN}

Content-Type: application/json

1. Send a Push Notification

Send a notification to all subscribers of a channel.

Write to

/tmp/pushinator_request.json

:

{

"channel_id"

:

""

,

"content"

:

"Hello from Pushinator!"

}

Replace

with your actual channel UUID, then run:

curl

-s

-X

POST

"https://api.pushinator.com/api/v2/notifications/send"

\

--header

"Authorization: Bearer

${PUSHINATOR_TOKEN}

"

\

--header

"Content-Type: application/json"

\

-d

@/tmp/pushinator_request.json

Response:

{

"success"

:

true

,

"message"

:

"Notification created and being sent to subscribers"

}

2. Send Deployment Notification

Notify when a deployment completes.

Write to

/tmp/pushinator_request.json

:

{

"channel_id"

:

""

,

"content"

:

"Deployment complete! Project deployed to production."

}

Replace

with your actual channel UUID, then run:

curl

-s

-X

POST

"https://api.pushinator.com/api/v2/notifications/send"

\

--header

"Authorization: Bearer

${PUSHINATOR_TOKEN}

"

\

--header

"Content-Type: application/json"

\

-d

@/tmp/pushinator_request.json

3. Send Alert with Emoji

Include emojis for visual distinction.

Write to

/tmp/pushinator_request.json

:

{

"channel_id"

:

""

,

"content"

:

"Build failed! Check the CI logs."

}

Replace

with your actual channel UUID, then run:

curl

-s

-X

POST

"https://api.pushinator.com/api/v2/notifications/send"

\

--header

"Authorization: Bearer

${PUSHINATOR_TOKEN}

"

\

--header

"Content-Type: application/json"

\

-d

@/tmp/pushinator_request.json

Request Parameters

Parameter

Type

Required

Description

channel_id

string

Yes

UUID of the notification channel

content

string

Yes

Notification message text

HTTP Status Codes

Code

Description

2xx

Success - notification sent

4xx

Invalid request or missing parameters

5xx

Server error - retry recommended

Guidelines

Keep messages concise

Push notifications have limited display space

Use channels for topics

Create separate channels for different notification types

Rate limiting

Stay within your plan's monthly notification limit

Include context

Make notifications actionable with relevant details