For Agents
Create polls, collect votes, retrieve results, and moderate comments on the Crowdsignal polling platform.
Get started with Crowdsignal API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a Crowdsignal poll"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Crowdsignal API API.
Create new polls and update existing poll configurations via /CreatePoll and /UpdatePoll
Retrieve poll results in aggregate or per-vote via /GetPollResults and /GetPollVotes
Reset poll results to start a fresh data collection round
List and moderate poll comments using /GetPollComments and /ModerateComment
GET STARTED
Use for: I need to create a new Crowdsignal poll, Get the results for a specific poll ID, List all polls in our Crowdsignal account, Moderate a flagged comment on a poll
Not supported: Does not handle long-form survey logic, conjoint analysis, or panel recruitment — use for Crowdsignal polls, ratings, and basic comment moderation only.
Jentic publishes the only available OpenAPI document for Crowdsignal API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Crowdsignal API, keeping it validated and agent-ready. Crowdsignal is an Automattic-owned polls, ratings, and surveys product, popular with WordPress publishers. The API exposes 16 POST endpoints for creating, updating, listing, and deleting polls, collecting and resetting votes, retrieving comments, moderating comments, and managing account and folder metadata. Authentication is by partnerGUID query parameter rather than an Authorization header.
Register a vote on a poll programmatically with /Vote
Manage account-level metadata and folders via /GetAccount, /UpdateAccount, and /GetFolders
Patterns agents use Crowdsignal API API for, with concrete tasks.
★ Programmatic Poll Creation for Editorial Workflows
Auto-publish polls alongside articles in a CMS by calling POST /CreatePoll with the question and answer set, then embedding the returned poll into the article body. Editorial ops teams use this to remove the manual UI step from a high-frequency publishing flow, and POST /UpdatePoll handles late edits to either the question or the answer choices.
Create a Crowdsignal poll with question 'Which release notes feature stands out?' and three answer choices, returning the poll ID
Vote and Comment Aggregation
Aggregate poll results into a reporting dashboard by polling /GetPollResults at regular intervals and pulling per-vote breakdowns through /GetPollVotes. Editorial and audience-research teams use this to push poll data into BI tools, and /GetPollComments plus /ModerateComment let a moderator clean up spam without touching the Crowdsignal UI.
Fetch results for poll ID 12345 via /GetPollResults and reject any pending comments via /ModerateComment whose body contains a banned word
Multi-Property Polling Account Management
Manage a single Crowdsignal account that powers polls across many properties by listing folders with /GetFolders and updating account-level settings via /UpdateAccount. Larger publishers organise polls by property or campaign through folders so reporting stays clean.
List Crowdsignal folders and update the account email address to ops@example.com
AI Agent Survey Result Summaries
An AI agent assembles a Monday-morning summary of the prior week's poll activity by calling Crowdsignal through Jentic. The agent searches for the crowdsignal_get_poll_results operation, executes against the team's vaulted partnerGUID, and joins the results with poll titles to produce a markdown summary. Jentic injects the partnerGUID query parameter so the agent never sees the raw key.
Use the Jentic SDK to fetch results for every poll created in the last 7 days and summarise top-voted answers per poll
16 endpoints — jentic publishes the only available openapi specification for crowdsignal api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/CreatePoll
Create a new poll
/UpdatePoll
Update an existing poll
/GetPollResults
Retrieve aggregated poll results
/GetPollVotes
Retrieve individual poll votes
/Vote
Register a vote on a poll
/GetPollComments
Retrieve comments on a poll
/ModerateComment
Approve or reject a comment
/CreatePoll
Create a new poll
/UpdatePoll
Update an existing poll
/GetPollResults
Retrieve aggregated poll results
/GetPollVotes
Retrieve individual poll votes
/Vote
Register a vote on a poll
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Crowdsignal partnerGUID is held encrypted in the Jentic vault. Agents receive a scoped execution token and Jentic appends the partnerGUID query parameter at request time so the raw key never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'create a Crowdsignal poll' or 'get poll results' and Jentic returns the matching Crowdsignal operation with its input schema, removing the need to read the Crowdsignal docs.
Time to first call
Direct Crowdsignal integration: half a day for partnerGUID setup and the unusual all-POST API shape. Through Jentic: under an hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
crowd.dev API
crowd.dev tracks community activity that can include responses to Crowdsignal polls
Use Crowdsignal to collect poll responses and crowd.dev to log those responses as community activities tied to a member.
Crove API
Crove generates documents that can summarise Crowdsignal poll results into a templated report
Pair Crowdsignal results data with Crove document templates when an agent needs to produce a recurring polled-results report.
Cron-job.org API
cron-job.org schedules recurring HTTP calls into Crowdsignal for periodic results sync
Use cron-job.org to schedule a daily Crowdsignal /GetPollResults call when an agent doesn't host its own scheduler.
Specific to using Crowdsignal API API through Jentic.
Why is there no official OpenAPI spec for Crowdsignal API?
Crowdsignal does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crowdsignal API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Crowdsignal API use?
The Crowdsignal API authenticates via a partnerGUID query parameter rather than a header — your API key is appended to each request as ?partnerGUID=YOUR_KEY. Through Jentic the partnerGUID is held encrypted in the vault and Jentic appends it at request time so it never enters the agent's context.
Can I create a poll and retrieve its results through the API?
Yes. POST /CreatePoll creates a poll, and POST /GetPollResults returns aggregated results for a poll ID, while POST /GetPollVotes returns the per-vote breakdown for analysis.
How do I create a poll through Jentic?
Search Jentic for 'create a Crowdsignal poll', load the operation schema for POST /CreatePoll, and execute with the question and answer set. Jentic appends the partnerGUID query parameter automatically.
How many endpoints does the Crowdsignal API expose?
Sixteen POST endpoints covering polls, votes, results, comments, comment moderation, accounts, folders, and the /pdInitiate and /GetUserCode bootstrap calls.
Can I moderate poll comments through the API?
Yes. POST /GetPollComments lists comments on a poll and POST /ModerateComment approves or rejects a specific comment, so a moderation pipeline can run without using the Crowdsignal UI.
/GetPollComments
Retrieve comments on a poll
/ModerateComment
Approve or reject a comment