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

# Spinitron v2 API

Notes **Tutorial demo** using this API is at [https://spinitron.com/v2-api-demo/](https://spinitron.com/v2-api-demo/). For web integration using iframes and/or JavaScript instead of an API, see [https://spinitron.github.io/v2-web-integration/](https://spinitron.github.io/v2-web-integration/). **Your API key** is found in the Spinitron web app. Log in to Spinitron and go to *Automation & API* in th. The API exposes 9 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically get personas, get persona by id. Covers 9 operations with apiKey, bearer authentication.

## Scope

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

## Capabilities

- Get Personas
- Returns scheduled shows optionally filtered by {start} and/or {end} datetimes
- Log a Spin
- Query and filter Spinitron v2 API records by parameters
- Monitor Spinitron v2 API operational status and events

## Use cases

### Developer Tools Operations

Use the Spinitron v2 API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get personas, get persona by id, returns scheduled shows optionally filtered by {start} and/or {end} datetimes.

Example prompt: Call GET /personas to get personas

### Automated Persona Management

Automate persona operations by combining multiple Spinitron v2 API endpoints. Agents can get persona by id and then returns scheduled shows optionally filtered by {start} and/or {end} datetimes in a single workflow.

Example prompt: Call GET `/personas/{id}` to get persona by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Spinitron v2 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, bearer tokens manually.

Example prompt: Search Jentic for 'get personas', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/personas` | Get Personas |
| GET | `/personas/{id}` | Get Persona by id |
| GET | `/shows` | Returns scheduled shows optionally filtered by {start} and/or {end} datetimes |
| GET | `/shows/{id}` | Get a Show by id |
| GET | `/playlists` | Returns playlists optionally filtered by {start} and/or {end} datetimes |
| GET | `/playlists/{id}` | Get a Playlist by id |
| POST | `/spins` | Log a Spin |
| GET | `/spins` | Returns spins optionally filtered by {start} and/or {end} datetimes |

## Key resources

- **Persona** — Operations related to Persona
- **Show** — Operations related to Show
- **Playlist** — Operations related to Playlist
- **Spin** — Operations related to Spin

## Why Jentic

- **Setup:** Wiring the Spinitron v2 API by hand means handling both its query-string access token and JWT bearer auth, and pointing every call at the spinitron.com/api host yourself. Through Jentic you install once, import the Spinitron v2 API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Spinitron puts the resource id in the URL path (`/shows/{id}`, `/playlists/{id}`), so a rule can pin your agent to reading one show or playlist. You choose the operations it may call, so posting new spins is not included unless you add it.
- **Credential handling:** Your Spinitron access 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.
- **Discovery method:** Agents search Jentic by intent such as 'list DJ personas' or 'get a show's playlists', and Jentic returns the matching Spinitron v2 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 Spinitron v2 API use?

The Spinitron v2 API uses apiKey, bearer authentication. 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 get personas with the Spinitron v2 API?

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

### What are the rate limits for the Spinitron v2 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 get personas through Jentic?

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

### How many endpoints does the Spinitron v2 API have?

The Spinitron v2 API exposes 9 endpoints covering persona, show, playlist operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Spinitron operations and credentials the agent may use. Because Spinitron puts the resource id in the URL path, such as GET `/shows/{id}` and GET `/playlists/{id}`, you can pin the agent to reading a single show or playlist. You also choose the operations it may call, so writing new records with POST /spins stays off unless you add it.