← Back to catalog

Other

Spinitron v2

auto-generated
swirls add spinitron
actionGETv1.0.0

Get a Playlist by id

The response object represents the playlist specified by {id}. Status 404 is returned if a playlist with {id} does not exist or if it does but starts in the future (with allowed tolerance equals 1 hour in future).

Source
actionGETv1.0.0

Get a Show by id

The response object represents the next occurence of the show specified by {id}. Status 404 is returned if a show with {id} does not exist or if it does but all its scheduled occurences elapsed in the past.

Source
actionPOSTv1.0.0

Log a Spin

An endpoint for automation systems to log spins into the spin table.

Source
actionGETv1.0.0

Returns scheduled shows optionally filtered by {start} and/or {end} datetimes

**Terminology**: Spinitron defines a *show* as a radio program. A show can have one or more *schedules*, each of which may specify either an *occurence* or a *repetition*, which represents a set of occurences. Thus scheduled shows have occurences that, for example, may be displayed in a calendar. In the response, `items` is an array of objects representing occurences of scheduled shows. You may optionally filter `items` to a datetime *range* by including in the request {start} and/or {end} parameters, both of which must be no more than one hour in the past. An occurence starting at {end} is included in the reponse. `itmes` can include occurences that begin *or* end within the filter range. A show that goes on air before {start} appears in `items` if it ends *after* but not *at* {start}. An occurence starting at or before {end} is included. If the request omits the {start} parameter, the server sets its value to the current time so that the filter range's start is always defined. If the request specifies {end} then the requested range is *bounded*, otherwise it is *unbounded*. For a bounded request, `items` includes *every* occurence of all shows occuring in the range. The only difference between objects in `items` representing a given show will be the `start` field value. For an unbounded request, `items` includes *only one* occurence per show, specifically, the next occurrence after {start} of all shows occuring after {start}. Use an unbounded request to get a straight list all shows. Use a bounded request to get a calendar/agenda of shows expanded into occurrences by thir shedules and repetitions. Objects in `items` are ordered first by `datetime` and then by `id`.

Source
Beyond the catalog

Any provider, on request.

01

Request it

Tell us which provider you need, and we will ship it in the registry.

02

Generate it

Point swirls add at an OpenAPI or GraphQL spec. Typed actions for any API you hold credentials for, today.

acme · integrations
terminal
~/acme $swirls add linear
✓ 12 typed actions · scopes and schemas included
 
~/acme $swirls add https://api.acme.dev/openapi.json
◆ Fetched spec · 38 operations
✓ 6 typed actions · generated from spec