canonical: https://jentic.com/apis/sondar.io/sondar

# Sondar

Sondar is an AI-powered customer feedback analyst that turns mountains of feedback into clear, actionable insights. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically import a ticket via zapier, list bundles. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- Import a ticket via Zapier
- List bundles
- Authenticate with API key
- Query and filter Sondar records by parameters
- Monitor Sondar operational status and events

## Use cases

### Analytics Operations

Use the Sondar to perform analytics operations programmatically. The API provides 3 endpoints covering core functionality including import a ticket via zapier, list bundles, authenticate with API key.

Example prompt: Call POST `/wf/zapier-import-ticket` to import a ticket via zapier

### Automated Workflow Management

Automate workflow operations by combining multiple Sondar endpoints. Agents can list bundles and then authenticate with API key in a single workflow.

Example prompt: Call POST `/wf/list-bundles` to list bundles, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sondar 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 'import a ticket via zapier', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/wf/zapier-import-ticket` | Import a ticket via Zapier |
| POST | `/wf/list-bundles` | List bundles |
| POST | `/wf/authentication` | Authenticate with API key |

## Key resources

- **Workflow** — Use this to trigger a workflow
- **Data** — Use this to fetch, modify and delete data

## 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:** 43 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 40 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 42 / 100
- **View full report:** https://jentic.com/apis/sondar.io/sondar/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 Sondar by hand means passing its api_token query key on every call, pointing at the SwaggerHub-hosted base URL, and handling retries on its workflow endpoints yourself. Through Jentic you install once, import Sondar from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Sondar exposes workflow operations that carry their target in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as importing a ticket or listing bundles. You choose which operations are in the allowed set, so anything you do not add stays out of reach.
- **Credential handling:** Your Sondar 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 'import a ticket' or 'list bundles', and Jentic returns the matching Sondar 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 Sondar use?

The Sondar uses an API key passed in the `api_token` 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 import a ticket via zapier with the Sondar?

Yes. Use the POST `/wf/zapier-import-ticket` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sondar?

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 import a ticket via zapier through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'import a ticket via zapier'. Jentic returns the matching Sondar operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sondar have?

The Sondar exposes 3 endpoints covering workflow, data operations.

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

Yes. Because Jentic One is self-hosted, you decide which Sondar operations your agent may call and add only those to its allowed set. Sondar's workflow operations carry their target in the request body rather than in the URL, so you can grant just importing a ticket via POST `/wf/zapier-import-ticket` or listing bundles via POST `/wf/list-bundles` and leave everything else out of reach. The stored API key is injected at execution time under your own rules, so the agent can only exercise the operations you have permitted.