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

# Soundee Producer API

soundee.com/main version 1.0. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a coupon, update a coupon. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a coupon
- Update a coupon
- Get
- Me
- Monitor Soundee Producer API operational status and events

## Use cases

### Developer Tools Operations

Use the Soundee Producer API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including create a coupon, update a coupon, get.

Example prompt: Call POST /coupons to create a coupon

### Automated Cart Abandonments Management

Automate cart abandonments operations by combining multiple Soundee Producer API endpoints. Agents can update a coupon and then get in a single workflow.

Example prompt: Call PUT `/coupons/{id}` to update a coupon, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Soundee Producer 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 'create a coupon', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/coupons` | Create a coupon |
| PUT | `/coupons/{id}` | Update a coupon |
| GET | `/transactions` | Get |
| GET | `/` | Me |
| GET | `/email-captures` | Get |
| GET | `/cart-abandonments` | Get List |
| GET | `/transactions/{id}` | Get object |
| GET | `/cart-abandonments/{id_or_token}` | Get Object |

## Key resources

- **Cart Abandonments** — Operations for cart abandonments
- **Coupons** — Operations for coupons
- **Email Captures** — Operations for email captures
- **Transactions** — Operations for transactions

## 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:** 55 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 34 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 53 / 100
- **View full report:** https://jentic.com/apis/soundee.com/soundee/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 Soundee Producer API by hand means passing its x-api-key header on every call, pointing at the api.soundee.com/me host, and handling paging and retries across its coupon and transaction calls yourself. Through Jentic you install once, import the Soundee Producer API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Soundee Producer API puts resource ids in the URL path (`/coupons/{id}`, `/transactions/{id}`), so a rule can pin your agent to one coupon or transaction: it can read or update that resource and nothing else. You choose the operations it may call, so write operations like creating or updating a coupon are not included unless you add them.
- **Credential handling:** Your Soundee 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 'create a coupon' or 'list transactions', and Jentic returns the matching Soundee Producer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Soundee Producer API use?

The Soundee Producer API uses an API key passed in the `x-api-key` 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 create a coupon with the Soundee Producer API?

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

### What are the rate limits for the Soundee Producer 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 create a coupon through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a coupon'. Jentic returns the matching Soundee Producer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Soundee Producer API have?

The Soundee Producer API exposes 8 endpoints covering cart abandonments, coupons, email captures operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Soundee Producer API operations and credentials your agent may use. You choose the exact operations it can call, so write actions like creating a coupon (POST /coupons) or updating one (PUT `/coupons/{id}`) are left out unless you add them. Since the API carries resource ids in the path, such as `/coupons/{id}` and `/transactions/{id}`, a rule can pin the agent to a single coupon or transaction and let it read or update only that resource.