From 3568e62fab680ecbc81d1f96d93d5326403e74d8 Mon Sep 17 00:00:00 2001 From: sonallux <13821543+sonallux@users.noreply.github.com> Date: Tue, 24 Jun 2025 03:22:12 +0000 Subject: [PATCH] Automated update of Spotify's OpenAPI definition --- fixed-spotify-open-api.yml | 20 ++++++++++++++++++++ official-spotify-open-api.yml | 20 ++++++++++++++++++++ 2 files changed, 40 insertions(+) diff --git a/fixed-spotify-open-api.yml b/fixed-spotify-open-api.yml index f54aa35..d8d4958 100644 --- a/fixed-spotify-open-api.yml +++ b/fixed-spotify-open-api.yml @@ -1311,6 +1311,26 @@ paths: A JSON array of the [Spotify IDs](/documentation/web-api/concepts/spotify-uris-ids). For example: `["4iV5W9uYEdYUVa79Axb7Rh", "1301WleyT98MSxVHPZCA6M"]`
A maximum of 50 items can be specified in one request. _**Note**: if the `ids` parameter is present in the query string, any IDs listed here in the body will be ignored._ items: type: string + timestamped_ids: + type: array + description: | + A JSON array of objects containing track IDs with their corresponding timestamps. Each object must include a track ID and an `added_at` timestamp. This allows you to specify when tracks were added to maintain a specific chronological order in the user's library.
A maximum of 50 items can be specified in one request. _**Note**: if the `timestamped_ids` is present in the body, any IDs listed in the query parameters or the `ids` field in the body will be ignored._ + items: + type: object + required: + - id + - added_at + properties: + id: + type: string + description: | + The [Spotify ID](/documentation/web-api/concepts/spotify-uris-ids) for the track. + added_at: + type: string + format: date-time + x-spotify-docs-type: Timestamp + description: | + The timestamp when the track was added to the library. Use ISO 8601 format with UTC timezone (e.g., `2023-01-15T14:30:00Z`). You can specify past timestamps to insert tracks at specific positions in the library's chronological order. The API uses minute-level granularity for ordering, though the timestamp supports millisecond precision. responses: "200": description: Track saved diff --git a/official-spotify-open-api.yml b/official-spotify-open-api.yml index 572e58e..e8f6e8b 100644 --- a/official-spotify-open-api.yml +++ b/official-spotify-open-api.yml @@ -1348,6 +1348,26 @@ paths: A JSON array of the [Spotify IDs](/documentation/web-api/concepts/spotify-uris-ids). For example: `["4iV5W9uYEdYUVa79Axb7Rh", "1301WleyT98MSxVHPZCA6M"]`
A maximum of 50 items can be specified in one request. _**Note**: if the `ids` parameter is present in the query string, any IDs listed here in the body will be ignored._ items: type: string + timestamped_ids: + type: array + description: | + A JSON array of objects containing track IDs with their corresponding timestamps. Each object must include a track ID and an `added_at` timestamp. This allows you to specify when tracks were added to maintain a specific chronological order in the user's library.
A maximum of 50 items can be specified in one request. _**Note**: if the `timestamped_ids` is present in the body, any IDs listed in the query parameters or the `ids` field in the body will be ignored._ + items: + type: object + required: + - id + - added_at + properties: + id: + type: string + description: | + The [Spotify ID](/documentation/web-api/concepts/spotify-uris-ids) for the track. + added_at: + type: string + format: date-time + x-spotify-docs-type: Timestamp + description: | + The timestamp when the track was added to the library. Use ISO 8601 format with UTC timezone (e.g., `2023-01-15T14:30:00Z`). You can specify past timestamps to insert tracks at specific positions in the library's chronological order. The API uses minute-level granularity for ordering, though the timestamp supports millisecond precision. responses: '200': description: Track saved