Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

7digital Playlists API

Partner-level playlist management — create, list, update and add tracks.

7digital Playlists API is one of 23 APIs that 7digital publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Playlists. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a JSON-LD context, code examples, and 2 JSON Schemas.

This API exposes 4 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.0.3, at version 1.2.

Requests are made against a single base URL, https://api.7digital.com/1.2.

4 operations 3 paths 7 schemas 1 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.2
Base URL
https://api.7digital.com/1.2
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

7digital Playlists API declares 3 security schemes for authenticating requests. An API key is passed in the query as oauth_consumer_key (oauth1). An API key is passed in the query as oauth_consumer_key (oauth1_two_legged). An API key is passed in the query as oauth_consumer_key (oauth1_three_legged). By default, every request must be authenticated.

  • oauth1 — 7digital uses OAuth 1.0 signing. Every request MUST include oauthconsumerkey as either a query parameter or in the Authorization header. Sensitive operations r…
  • oauth1_two_legged — 2-legged OAuth 1.0 (partner-scoped — consumer key + secret only).
  • oauth1_three_legged — 3-legged OAuth 1.0 (consumer key + secret plus a user access token + secret).

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Playlists 4

Partner-level playlist management — create, list, update and add tracks.

GET
/playlists
7digital List Playlists
listPlaylists 3 params → 200
POST
/playlists
7digital Create Playlist
createPlaylist 1 param body → 201
PUT
/playlists/{playlistId}
7digital Update Playlist Details
updatePlaylistDetails 1 param body → 200
POST
/playlists/{playlistId}/tracks
7digital Add Tracks To Playlist
addTracksToPlaylist 1 param body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Playlist (9 properties), PlaylistTrackInput (6 properties), PlaylistListResponse (5 properties), CreatePlaylistRequest (4 properties). Each schema is shown below with its type and property counts.

PlaylistTrack
UpdatePlaylistRequest
object
3 properties
AddTracksRequest
object
1 property 1 required
PlaylistTrackInput
object
6 properties 3 required
CreatePlaylistRequest
object
4 properties 1 required
Playlist
object
9 properties
PlaylistListResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

7digital-playlists-api-openapi.yml Raw ↑

Other APIs 7digital publishes across the network.

7digital Artists API
7digital Basket API
7digital Catalogue API
7digital Content Delivery API
7digital Download Purchases API
7digital Editorial API
7digital Interactive Radio API
7digital IpLookup API
7digital Logging API
7digital Offline Devices API
7digital Payment API
7digital Releases API