Pulseri REST API to send people and events, read answers
Send people and events from your code, and read answers and score reports back.
What it does
The REST API lets your code talk to Pulseri. Send people and events as they happen, and either can start a survey. Read answers and reports back into your own tools. Lists use the same paging, search and filters everywhere, and errors share one shape.
First requests
Tell Pulseri who someone is, then what they did. A public key can send people in, and a service account key on your server sends events.
curl https://api.pulseri.com/v1/identify \
-H "Authorization: Bearer pk_live_..." \
-H "Content-Type: application/json" \
-d '{
"external_id": "user_123",
"name": "Emily Carter",
"email": "[email protected]",
"group_id": "northwind-books",
"traits": { "plan": "pro", "seats": 12 }
}'
Customers and employees
/identify takes an optional audience_type: customer (the default) or employee. /group takes customer_account (the default) or department. Pulseri uses the value only when it creates the person or group; on an existing one it is ignored. A customer joins a customer account and an employee joins a department, and a group that /identify creates from group_id gets the matching type. If the group already exists with the other type, a secret key or a signed request gets 422 group_audience_mismatch. An unsigned public key still gets 204 No Content and the person is saved without the group.
Identity verification
A public key is visible in your page, so Pulseri lets you sign requests. Compute HMAC-SHA256(secret, message) as lowercase hex on your server and send it as signature to /identify, /group or /track. The message is person:<id> for a person (/identify, /track) and group:<id> for a group (/group). Public-key calls to /identify and /group answer 204 No Content. How signing works
Who it suits
Developers who want feedback to follow what happens in their product.
What you can do
Most of the dashboard is in the API. The API reference lists every call.
Send people and groups
Identify a person with their traits and group them by company or team.
Send events
Tell Pulseri what happened, such as a ticket closing, so a trigger can start a survey.
Read answers and reports
Fetch answers and score reports for one campaign, one group or one person.
Manage your setup
Work with segments, campaigns, alert rules, webhook endpoints and your team.
How to set it up
Most people finish in minutes.
- Create a key in the dashboard. A public key is for browser code and can only send data in. A service account key is for your server. It can send data whatever its role, so keep it out of browsers and shared tools.
- Send the key as a Bearer token in each request's Authorization header.
- Tell Pulseri who someone is, then what they did.
- Create a trigger in Pulseri for that event, choose the survey and add a delay if you like.
- Read answers and score reports back through the same API.
Which plans have it
This comes from the current plan table.
All plansSee plans and pricing
Common questions
Works well with
Signed webhooks
Send events in, and get alerts out, with a signature on every request.
Build your own
All plansAI assistants
Ask about your feedback in plain words from the assistant you already use.
Build your own
All plans
Try it on your own feedback
Start a free trial and connect it today.
Free for 14 days. Cancel any time before it ends.