Alchemer REST API

Name: Alchemer REST API
Brand: Alchemer REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms SurveysapiKey13 EndpointsREST

For Agents

Create and manage Alchemer surveys, retrieve responses and statistics, and work with contact lists used to send survey campaigns.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Alchemer REST API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.

Alchemer REST API

Connect the Alchemer REST API to your agent

Capabilities

Start building with Alchemer REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs