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

# Survicate Data Export API

The Survicate Data Export API allows you to retrieve survey data, responses, respondent information, and manage personal data. The API provides REST-based endpoints for accessing feedback collected through Survicate surveys. The API exposes 9 endpoints secured with basic authentication.

## For AI agents

Programmatically list all surveys, retrieve survey information. Covers 9 operations with basic authentication.

## Scope

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

## Capabilities

- List all surveys
- Retrieve survey information
- Integrate Survicate Data Export API into automated workflows
- Query and filter Survicate Data Export API records by parameters
- Monitor Survicate Data Export API operational status and events

## Use cases

### Social Media Operations

Use the Survicate Data Export API to perform social media operations programmatically. The API provides 9 endpoints covering core functionality including list all surveys, retrieve survey information, list questions.

Example prompt: Call GET /surveys to list all surveys

### Automated Survey Management

Automate survey operations by combining multiple Survicate Data Export API endpoints. Agents can retrieve survey information and then list questions in a single workflow.

Example prompt: Call GET /surveys/{survey_id} to retrieve survey information, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Survicate Data Export 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 basic tokens manually.

Example prompt: Search Jentic for 'list all surveys', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /surveys | List all surveys |
| GET | /surveys/{survey_id} | Retrieve survey information |
| GET | /surveys/{survey_id}/questions | List questions |
| GET | /responses | List all responses |
| GET | /responses/{response_id} | Retrieve a response |
| GET | /respondents/{respondent_id}/attributes | List respondent's attributes |
| GET | /respondents/{respondent_id}/responses | List respondent's responses |
| GET | /personal-data/counters | Get personal data counters |

## Key resources

- **Survey** — Operations for managing and retrieving survey information
- **Response** — Operations for accessing survey responses
- **Respondent** — Operations for managing respondent data
- **Personal Data** — Operations for GDPR compliance and personal data management

## Why Jentic

- **Setup:** Wiring the Survicate Data Export API by hand means setting up HTTP basic auth against the data-api.survicate.com host and paging through surveys, responses, and respondent attributes yourself. Through Jentic you install once, import the Survicate Data Export API from the API Directory, store the basic credential once, and your agent calls it.
- **Permission scoping:** Survicate puts the survey, response, and respondent id in the URL path (/surveys/{survey_id}, /responses/{response_id}, /respondents/{respondent_id}/...), so a rule can pin your agent to one survey or respondent. Every operation here is a read, so the agent can list and fetch export data and nothing beyond the read operations you allow.
- **Credential handling:** Your Survicate basic credential 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 'list all surveys' or 'get a respondent's responses', and Jentic returns the matching Survicate operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Survicate Data Export API use?

The Survicate Data Export API uses HTTP Basic authentication with username and password. 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 list all surveys with the Survicate Data Export API?

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

### What are the rate limits for the Survicate Data Export 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 list all surveys through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all surveys'. Jentic returns the matching Survicate Data Export API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Survicate Data Export API have?

The Survicate Data Export API exposes 9 endpoints covering survey, response, respondent operations.

### Can I limit what my agent is allowed to do with the Survicate Data Export API?

Yes. Because you run Jentic One yourself, your own rules decide which Survicate operations and credentials the agent may use. Since Survicate carries the survey, response, and respondent id in the URL path (/surveys/{survey_id}, /responses/{response_id}, /respondents/{respondent_id}/attributes), you can pin the agent to a single survey or respondent and expose only the specific read calls you approve. Every Survicate endpoint here is read-only, so the agent can list and fetch export data and nothing beyond the reads you allow.