Surveysparrow API Documentation
✓ Official Vendor SpecIdentity AuthAuthorizationbearer251 EndpointsREST
For Agents
Programmatically list audit logs, create contact list. Covers 251 operations with bearer authentication.
Use for: I need to audit logs, I want to contact list, Search for contact lists, Find all contact
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
--- **Introduction** SurveySparrow API allows you to integrate third party applications in your enterprise ecosystem and helps you to automate workflows like, sending a survey when a ticket is closed or a employee leaves the organisation. Request & Response Format SurveySparrow API accepts HTTPS requests with JSON Arguments. The response will be in JSON format. Our Authentication is based on OAuth. The API exposes 251 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the API Documentation to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Documentation, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 API Documentation API.
List audit logs
Create contact list
Get Contacts
Query and filter API Documentation records by parameters
Monitor API Documentation operational status and events
Use Cases
Patterns agents use API Documentation API for, with concrete tasks.
★ Identity and Authentication Operations
Use the API Documentation to perform identity auth operations programmatically. The API provides 251 endpoints covering core functionality including list audit logs, create contact list, list contact lists.
Call GET /v1/audit-logs to list audit logs
Automated accounts Management
Automate accounts operations by combining multiple API Documentation endpoints. Agents can create contact list and then list contact lists in a single workflow.
Call POST /v1/contactlist to create contact list, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Documentation 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 bearer tokens manually.
Search Jentic for 'list audit logs', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
251 endpoints — --- **introduction** surveysparrow api allows you to integrate third party applications in your enterprise ecosystem and helps you to automate workflows like, sending a survey when a ticket is closed or a employee leaves the organisation.
METHOD
PATH
DESCRIPTION
GET
/v1/audit-logs
List audit logs
POST
/v1/contactlist
Create contact list
GET
/v1/contactlist
List contact lists
POST
/v1/contacts
Create contact
GET
/v1/contacts
Get Contacts
GET
/v1/roles
List roles
POST
/v1/surveys
Create survey
GET
/v1/surveys
Get surveys
GET
/v1/audit-logs
List audit logs
POST
/v1/contactlist
Create contact list
GET
/v1/contactlist
List contact lists
POST
/v1/contacts
Create contact
GET
/v1/contacts
Get Contacts
GET
/v1/roles
List roles
POST
/v1/surveys
Create survey
GET
/v1/surveys
Get surveys
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your SurveySparrow bearer token 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.
Intent-based discovery
Agents search Jentic by intent such as 'list audit logs' or 'create a contact list', and Jentic returns the matching SurveySparrow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using API Documentation API through Jentic.
What authentication does the API Documentation use?
The API Documentation uses a Bearer token in the Authorization header. 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 audit logs with the API Documentation?
Yes. Use the GET /v1/audit-logs endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Documentation?
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 audit logs through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list audit logs'. Jentic returns the matching API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API Documentation have?
The API Documentation exposes 251 endpoints covering accounts, audit_logs, ces operations.
Can I limit what my agent is allowed to do with the SurveySparrow API?
Yes. Because you run Jentic One yourself, your own rules decide which SurveySparrow operations and credentials the agent may use. Since each operation carries its target in the request body or query, you scope the agent to only the calls it needs, such as GET /v1/surveys to list surveys or GET /v1/audit-logs to read audit logs. A write like POST /v1/contacts or POST /v1/contactlist is available only if you explicitly add it to that set.
GET STARTED