canonical: https://jentic.com/apis/polly.ai/polly-api

# Polly Web API

Polly is a collaboration tool that runs inside Slack and Microsoft Teams, enabling teams to create polls, surveys, and automated workflows without leaving their chat workspace. The Polly Web API provides programmatic control over poll creation, response collection, survey distribution, and results analysis. Product teams use it to automate recurring stand-ups, retrospectives, and pulse checks. HR departments deploy engagement surveys and feedback workflows that trigger based on employee milestones. The API supports multiple question types including multiple choice, rating scales, open text, and ranked preference. It enables integration with BI tools to analyze response trends, trigger notifications based on survey scores, and archive poll data for compliance. Polly's anonymous response option makes it suitable for sensitive feedback scenarios where psychological safety is critical.

## For AI agents

Create and manage polls, surveys, and team feedback workflows within Slack and Microsoft Teams workspaces.

## Scope

Provides poll and survey creation within Slack and Microsoft Teams workspaces. Does not handle direct messaging to users, file uploads, or channel management-use Slack/Teams APIs for those capabilities.

## Capabilities

- Create polls with multiple choice, rating, or open-text questions
- Schedule recurring polls for stand-ups, retrospectives, or pulse checks
- Retrieve poll responses and aggregate results in real-time
- Manage surveys with multi-question logic and branching paths
- Configure anonymous response collection for sensitive feedback
- List all polls and surveys for a workspace with filtering by status
- Delete polls or archive survey data for compliance requirements

## Use cases

### Automated Daily Stand-ups and Team Check-ins

Engineering teams use Polly to replace synchronous stand-up meetings with asynchronous polls that collect status updates, blockers, and mood signals. The API enables creating recurring polls that post at 9am daily, ask structured questions about yesterday's work and today's plans, and compile responses into a digest. Team leads query the API to retrieve responses, identify blockers mentioned across multiple team members, and trigger follow-up threads. This reduces meeting overhead for distributed teams across time zones while maintaining alignment visibility.

Example prompt: Create recurring Polly poll scheduled for weekday mornings asking 'What did you complete yesterday?', 'What are you working on today?', and 'Any blockers?', post to engineering Slack channel, retrieve responses daily, summarize blockers for team lead.

### Sprint Retrospective and Team Health Surveys

Agile teams conduct sprint retrospectives using Polly surveys with rating scales for process effectiveness, team collaboration, and work-life balance. The API allows creating retrospective surveys with branching logic-if someone rates 'team morale' below 3, they see follow-up open-text questions exploring the issue. Scrum masters use the API to retrieve anonymized responses, analyze sentiment trends across sprints, and export data to BI tools for long-term team health tracking. This creates psychological safety for honest feedback while providing quantitative metrics for continuous improvement.

Example prompt: Create Polly survey with rating questions on sprint velocity, team collaboration, and satisfaction, enable anonymous responses, post to team Slack channel at sprint end, retrieve results, export to Tableau for trend analysis.

### Employee Engagement and Pulse Check Programs

HR teams deploy monthly or quarterly pulse surveys to measure employee engagement, manager effectiveness, and organizational trust. The API enables creating multi-question surveys with eNPS (Employee Net Promoter Score) questions, department-specific routing, and demographic segmentation. Automated workflows use the API to distribute surveys based on employee start dates, trigger alerts when responses indicate flight risk, and aggregate results by team or location. This provides early warning signals for retention issues and validates impact of culture initiatives.

Example prompt: Create monthly Polly pulse survey with eNPS question and open feedback field, schedule distribution to all-company Slack channel on first Monday of month, collect responses, calculate eNPS score, trigger alert to HR if score drops below threshold.

### Product Research and User Feedback Collection

Product managers use Polly to gather quick feedback from internal beta testers or customer advisory groups within dedicated Slack channels. The API supports creating feature preference polls (e.g., 'Which dashboard layout do you prefer?'), usability rating scales, and open-ended feature request questions. Responses flow into product management tools via webhooks or API polling. This enables rapid iteration cycles where designers share prototypes, collect structured feedback within hours, and validate decisions before engineering commitment.

Example prompt: Create Polly poll showing three UI mockup options, post to customer advisory Slack channel, collect preference votes, retrieve results with timestamps, tally votes by user segment, share winner with design team.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/polls.create` | Create a new poll |
| GET | `/polls.list` | List all polls with optional filters |
| GET | `/polls.info` | Get details for a specific poll including responses |
| DELETE | `/polls.delete` | Delete a poll |
| POST | `/surveys.create` | Create a multi-question survey |

## Key resources

- **Polls** — Create, list, retrieve, and delete quick polling questions.
- **Surveys** — Manage multi-question surveys with logic and branching.
- **Responses** — Retrieve and analyze poll and survey responses.

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/polly.ai/polly-api/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Polly Web API by hand means setting up bearer auth against api.polly.ai/v1 and coding its poll and survey calls yourself. Through Jentic you install once, import the Polly Web API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Polly identifies polls and surveys through request parameters rather than pinning one in the URL path, so scope the agent to the operations it needs, such as creating a poll or listing polls. You choose that set, so a destructive operation like poll deletion is included only if you add it while a read-only agent keeps just the list and info operations.
- **Credential handling:** Your Polly token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a team standup poll' or 'list existing polls', and Jentic returns the matching Polly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Slack Web API** — Slack Web API provides messaging, channel management, and workspace administration capabilities.
- **Typeform API** — Typeform provides form and survey creation with conversational interfaces and advanced logic.
- **SurveyMonkey API** — SurveyMonkey provides enterprise survey distribution with advanced analytics and benchmarking.

## FAQ

### What authentication does the Polly API use?

The Polly API uses Bearer token authentication. You generate an API token from your Polly workspace settings in Slack or Teams, then pass it in the Authorization header for all requests.

### Can I create recurring polls with the Polly API?

Yes, the polls.create endpoint supports scheduling parameters that enable daily, weekly, or custom recurring polls. You specify the schedule cadence and the poll posts automatically to your designated Slack channel or Teams conversation.

### How does anonymous response collection work in Polly?

When you enable anonymous mode on a poll or survey, Polly collects responses without storing user identifiers. The API returns aggregated results without attribution, ensuring respondents feel safe providing honest feedback on sensitive topics.

### Can I integrate Polly poll results with BI tools like Tableau?

Yes, use the polls.info endpoint to retrieve response data in JSON format with timestamps and response values. Export this data to CSV or push it directly to BI platforms via their APIs for trend analysis and visualization.

### How do AI agents use the Polly API through Jentic?

Agents search Jentic for tasks like 'create a daily standup poll' and receive Polly operation schemas. Jentic securely stores the API token, handles authentication, and allows agents to create polls, retrieve responses, and analyze feedback trends with natural language instructions.

### Can I limit what my agent is allowed to do with the Polly API?

Yes. Because you run Jentic One yourself, your own rules decide which Polly operations and credentials the agent may use, and Polly identifies each poll or survey through request parameters rather than a fixed URL path. You choose the exact set the agent can call, so a read-only agent keeps just the list and info operations while creating a poll or survey is added only when you want it. A destructive operation like poll deletion is included only if you explicitly grant it.