Ask a question. Find out how it lands.

A pulsewave is one image and one question. The six emotions are fixed and identical everywhere, which is the point: results stay comparable across every pulsewave on the platform, and nobody can tilt an outcome by writing the answers.

You set a title, a category, an image, and how long voting stays open. Anyone can vote, with or without an account.

Public by default: it appears in the catalogue and anyone can vote. That is what you want for reach.

On the plans that allow it, a pulsewave can instead be private and restricted — to an age group, or to people whose email is on your company’s domain. Everyone else does not see it at all; it is filtered in the database, not hidden in the page.

Every pulsewave you own has its own analytics: the emotional split, who voted, when they voted, where from, and the written reasons. There is an AI summary over the free text, for when there is more of it than you want to read.

• Demographic — age and education of respondents
• Geographic — where the reactions came from
• Temporal — how the split moved over the hours
• Motivations — the written reasons
• Insights — a summary of the above

Results are exportable. What you never get is a list of who voted how — that is not a limitation of the export, it is the promise that makes people answer honestly.

Automatic publishing finds a trending image each morning and turns it into a pulsewave under your name, so your audience has something to react to on the days you do not post.

You choose whether it runs, how long each one stays open, and whether the next appears immediately or waits for the previous to close. It is off until you turn it on.

People can follow you, and are notified when you publish — filtered by the topics they chose to hear about.

On plans with messaging, someone who follows you can write to you and you can reply. You can also broadcast one message to all your followers at once. The asymmetry is intentional: nobody can message a creator who has not earned their interest.

Generate a key under Dashboard → API and authenticate with a bearer token. Keys are shown once and can be revoked at any time.

curl https://www.pulsogram.com/api/v1/me \
  -H "Authorization: Bearer YOUR_KEY"

Publish a pulsewave:

curl -X POST https://www.pulsogram.com/api/v1/pulsewaves \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "How does this make you feel?",
    "image_url": "https://example.com/image.jpg",
    "category": "Current Events"
  }'

Read the result:

curl https://www.pulsogram.com/api/v1/pulsewaves/PULSEWAVE_ID/stats \
  -H "Authorization: Bearer YOUR_KEY"

The six options are created for you, in the fixed order. Your monthly publishing limit applies exactly as it does in the interface — the API is another door into the same room, not a way around it.