Alchemer REST API
48
AI ReadinessFoundational (D+)48/100
Agent-ready OpenAPI document · curated by JenticProductivityForms SurveysapiKey13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create and manage Alchemer surveys, retrieve responses and statistics, and work with contact lists used to send survey campaigns.
Use for: I need to create a new survey in Alchemer, Retrieve all responses for a specific Alchemer survey, List the questions on a survey to map them to my own data model, Get aggregate statistics for a survey to populate a dashboard
Not supported: Does not handle email delivery infrastructure, advanced analytics dashboards, or quota and panel management - use for survey, response, and contact list operations only.
Jentic publishes the only available OpenAPI specification for Alchemer REST API, keeping it validated and agent-ready. The Alchemer REST API gives programmatic access to surveys, pages, questions, responses, campaigns, and contact lists in an Alchemer account. It supports listing and managing surveys, retrieving response data and aggregate statistics, and working with the contact lists used to distribute survey campaigns. Authentication uses an api_token and api_token_secret pair sent as query parameters on every request.
Install Jentic One Beta
Connect the Alchemer REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alchemer REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Falchemer.com%2Falchemer" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Falchemer.com%2Falchemer" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Alchemer REST API.
List and inspect Alchemer surveys, pages, and questions in an account
Create a new Alchemer survey with PUT /survey and update its configuration
Retrieve survey responses for a given survey id with /survey/{surveyId}/surveyresponse
Pull aggregate survey statistics for analysis or reporting dashboards
List survey campaigns attached to a survey to track distribution channels
Manage Alchemer contact lists and read the contacts inside a list for outreach
Use Cases
Patterns agents use Alchemer REST API for, with concrete tasks.
★ Sync survey responses to a data warehouse
A data team pulls responses from each active Alchemer survey on a schedule by calling /survey/{surveyId}/surveyresponse and writes them into a warehouse for analysis. Combining this with the survey statistics endpoint lets the team build dashboards that mix raw response rows with response rate and completion metrics. The integration removes manual CSV exports from the Alchemer UI.
GET /survey to list active surveys, then for each survey id GET /survey/{surveyId}/surveyresponse and append the rows to the warehouse table
Programmatic survey creation from a template
A research operations team uses the Alchemer REST API to create a new survey for each customer interview round by calling PUT /survey and then configuring questions and pages. This lets the team spin up surveys from a controlled template without clicking through the Alchemer designer for every project.
PUT /survey with the survey title and type, then GET /survey/{surveyId}/surveypage and /survey/{surveyId}/surveyquestion to verify the resulting structure
Contact list audit before a campaign send
Before launching an Alchemer email campaign, a marketing engineer audits the target contact list by listing every contact in /contactlist/{listId}/contactlistcontact and validating emails against an external suppression list. Only after the audit does the engineer attach the list to a campaign. This avoids sending to lapsed or invalid recipients.
GET /contactlist to find the target list id, then GET /contactlist/{listId}/contactlistcontact and pass each email to a validation step
Agent-driven survey reporting through Jentic
A Jentic agent receives an intent like 'show me last month's survey results' and chains the Alchemer operations: list surveys, fetch the matching survey, pull responses, and read aggregate statistics. The agent returns a concise summary to the user without exposing raw API tokens or response payloads.
Search Jentic for 'retrieve survey responses', load the schema for GET /survey/{surveyId}/surveyresponse, and execute it with the survey id resolved from a previous GET /survey call
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for alchemer rest api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/survey
List surveys
PUT
/survey
Create a survey
GET
/survey/{surveyId}
Retrieve a survey
GET
/survey/{surveyId}/surveyresponse
List survey responses
GET
/survey/{surveyId}/surveystatistic
Get aggregate survey statistics
GET
/contactlist
List contact lists
GET
/contactlist/{listId}/contactlistcontact
List contacts in a contact list
GET
/survey
List surveys
PUT
/survey
Create a survey
GET
/survey/{surveyId}
Retrieve a survey
GET
/survey/{surveyId}/surveyresponse
List survey responses
GET
/survey/{surveyId}/surveystatistic
Get aggregate survey statistics
GET
/contactlist
List contact lists
GET
/contactlist/{listId}/contactlistcontact
List contacts in a contact list
Jentic AI Readiness Score
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.
A
Alchemer REST API
- Foundational (D+)48/100
79
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
79
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
57%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Alchemer by hand means appending both api_token and api_token_secret as query parameters on every call, building survey and contact-list requests, and writing your own retry logic. Through Jentic you install once, import Alchemer from the API Directory, store both values once, and your agent calls it.
Permission scoping
Alchemer puts the survey and list ids in the URL path (/survey/{surveyId}/surveyresponse, /contactlist/{listId}/contactlistcontact), so a rule can pin your agent to one survey or contact list. You choose the operations it may call, so editing a survey is only included if you add it.
Credential isolation
Your Alchemer api_token and api_token_secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list survey responses', and Jentic returns the matching Alchemer operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Alchemer REST API through Jentic.
Why is there no official OpenAPI spec for Alchemer REST API?
Alchemer does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alchemer REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Alchemer REST API use?
Alchemer requires an api_token and api_token_secret pair, both sent as query parameters on every request. Jentic stores both values encrypted and injects them at execution time so neither token enters the agent's prompt context.
Can I retrieve all responses for a specific Alchemer survey?
Yes. Call GET /survey/{surveyId}/surveyresponse with the survey id you obtained from GET /survey. The endpoint returns the response rows for that survey, which you can paginate through and write into your own store.
What are the rate limits for the Alchemer REST API?
The OpenAPI spec does not declare rate limits. Alchemer enforces plan-based limits server-side (commonly documented as a few requests per second per token); throttle long-running exports and contact list reads accordingly.
How do I create a new survey with the Alchemer REST API through Jentic?
Search Jentic for 'create an alchemer survey', load the schema for PUT /survey, and execute it with the survey title and type. Jentic returns the new survey id so an agent can immediately follow up with question and page configuration calls.
Can I read the contacts in a specific Alchemer contact list?
Yes. Call GET /contactlist to find the list id, then GET /contactlist/{listId}/contactlistcontact to retrieve the contacts attached to that list.
Can I limit what my agent is allowed to do with the Alchemer REST API?
Yes. Because you run Jentic One yourself, your own rules decide which Alchemer operations and credentials the agent may use, so you can grant read-only calls like GET /survey/{surveyId}/surveyresponse and GET /contactlist/{listId}/contactlistcontact while withholding survey edits or deletes. Since Alchemer puts the survey and list ids in the URL path, a rule can also pin the agent to a single survey or contact list rather than the whole account. An operation such as updating a survey is available to the agent only if you explicitly include it.
GET STARTED