canonical: https://jentic.com/apis/survser.com/survser

# Survser Public API

Survser offers a powerful API that allows users to programmatically access survey data, enabling deeper integrations and custom analytics workflows. The API provides endpoints to retrieve survey responses and list surveys. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get survey responses, get surveys. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Get Survey Responses
- Manage analytics data programmatically
- Integrate Survser Public API into automated workflows
- Query and filter Survser Public API records by parameters
- Monitor Survser Public API operational status and events

## Use cases

### Analytics Operations

Use the Survser Public API to perform analytics operations programmatically. The API provides 2 endpoints covering core functionality including get survey responses, get surveys.

Example prompt: Call GET `/response/list` to get survey responses

### Data Retrieval and Monitoring

Query Survser Public API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Survser Public API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Survser Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get survey responses', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/response/list` | Get Survey Responses |
| GET | `/survey/list` | Get Surveys |

## Key resources

- **Surveys** — Operations for managing and retrieving surveys
- **Responses** — Operations for retrieving 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:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/survser.com/survser/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 Survser Public API by hand means attaching its query-string API key to every request against survser.com and parsing its survey and response lists yourself. Through Jentic you install once, import the Survser Public API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Both Survser operations are collection reads that take their filters in the query string, so scope your agent to the operations it needs, such as listing surveys or listing responses. You choose that set, so nothing beyond the read operations you allow is included.
- **Credential handling:** Your Survser API key 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 'get survey responses' or 'list my surveys', and Jentic returns the matching Survser operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Survser Public API use?

The Survser Public API uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get survey responses with the Survser Public API?

Yes. Use the GET `/response/list` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Survser Public API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get survey responses through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get survey responses'. Jentic returns the matching Survser Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Survser Public API have?

The Survser Public API exposes 2 endpoints covering surveys, responses operations.

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

Yes. Because Jentic One is self-hosted, you decide which Survser operations your agent may call, and both endpoints are read-only collection lists: GET `/survey/list` to list surveys and GET `/response/list` to get survey responses. Scope the agent to only the operation it needs, so an agent that just reads responses cannot list surveys unless you allow it. Your Survser API key is held by your own instance and injected at execution time, so the agent can never reach an operation you have not permitted.