canonical: https://jentic.com/apis/spream.co/spream

# Spream Zapier API

Spream is a membership platform for managing content, live streaming, and event reservations with integrated member authentication and payment processing. This API enables webhook management for Zapier integrations. The API exposes 3 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create zapier webhook, remove zapier webhook. Covers 3 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create Zapier webhook
- Remove Zapier webhook
- Get account info
- Query and filter Spream Zapier API records by parameters
- Monitor Spream Zapier API operational status and events

## Use cases

### Payments Operations

Use the Spream Zapier API to perform payments operations programmatically. The API provides 3 endpoints covering core functionality including create zapier webhook, remove zapier webhook, get account info.

Example prompt: Call POST `/zapier/webhooks` to create zapier webhook

### Automated Webhooks Management

Automate webhooks operations by combining multiple Spream Zapier API endpoints. Agents can remove zapier webhook and then get account info in a single workflow.

Example prompt: Call DELETE `/zapier/webhooks` to remove zapier webhook, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Spream Zapier 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 zapier webhook', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/zapier/webhooks` | Create Zapier webhook |
| DELETE | `/zapier/webhooks` | Remove Zapier webhook |
| GET | `/zapier/me` | Get account info |

## Key resources

- **Webhooks** — Manage Zapier webhooks for specified events
- **Account** — Get account information

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 60 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/spream.co/spream/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 Spream Zapier API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.spream.co/api/v1 host yourself. Through Jentic you install once, import the Spream Zapier API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Spream webhook endpoints take their target in the request body rather than as a resource in the URL path, so limit the agent to the operations it needs, such as reading your account with the me call or subscribing a webhook. You choose the operations it may call, so removing a webhook is not included unless you add it.
- **Credential handling:** Your Spream 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 'subscribe a Zapier webhook' or 'get my account details', and Jentic returns the matching Spream Zapier API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Spream Zapier API use?

The Spream Zapier API uses an API key passed in the `X-ZAPIER-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 zapier webhook with the Spream Zapier API?

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

### What are the rate limits for the Spream Zapier 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 zapier webhook through Jentic?

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

### How many endpoints does the Spream Zapier API have?

The Spream Zapier API exposes 3 endpoints covering webhooks, account operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Spream operations and credentials the agent may use, and you grant only the ones it needs. For example, you can allow the agent to read your account with the GET `/zapier/me` call and subscribe a webhook with POST `/zapier/webhooks`, while withholding DELETE `/zapier/webhooks` so it cannot remove webhooks. Since the webhook endpoints take their target in the request body rather than the URL path, scoping happens at the operation level, and the API key stays with your instance and is injected only for the calls you have permitted.