What's new

Changelog: what changed in the API and on this site

Every release since the July 2026 redesign, newest first, dated from this site's git history. Under each one, API lists what the public spec added, removed or changed, and Site what changed on these pages.

The reference documents API 1.2.0 RSS feed

  1. Your starred endpoints and recent runs, a cost calculator, and samples recorded this week

    For developers who come back while they build: what you starred and what you ran are one click from running again, /pricing turns a job into a price, and every recorded sample was made again this week.

    Site

    • A star on every operation page, and a Jump back in shelf under the home page's hero with your starred endpoints and recent runs. They are kept in this browser only.
    • The command palette opens on Starred and Recent runs; a recent run reopens the Run dialog with the query and path values you sent (request bodies are not kept).
    • A cost calculator on /pricing: pick a job (track metadata, play counts, monthly listeners or lyrics), say how many items and how often, and it works out the requests a month with the API's own batch caps, then the RapidAPI plan and the direct pack that cover it, with a checkout link.
    • Every recorded sample was recorded again on 22 October 2026 with the request the Run dialog sends, so the home page's code panel and every fallback show this week's numbers. /partner/track/count and /partner/tracks/count have recorded samples for the first time.
    • A guide to play counts: /spotify-play-count-api.
    • This page, with an RSS item per release and a dot on What's new when something changed since your last visit.
    • /charts labels the Top 200 as the daily chart it is, and each row's cover sits on a tile until it loads; the search page's suggestions show the artist or the cover they search for, and pages end with one short way to get a key.

  2. Snippets that authenticate, and checkout links that keep your pack

    The release that followed the 1.2.0 sync. Requests copied from the site now reach the API with your key, the direct buttons open checkout with the pack already chosen, and the guides were re-checked against the spec, Spotify's own pages and the platforms that sell the API.

    Site

    • Every curl snippet, and every Python one written with requests, sends your key in x-rapidapi-key to the /spotify-data base. Before, they sent it in a header the API does not read, to the bare host, so a pasted request answered 401.
    • Every Direct button opens the portal's checkout, and the ones that print a price open it on that pack. A Subscribe button on /pricing and the home page renews a pack through PayPal every 30 days, until you cancel it from the dashboard.
    • /pricing opens on a price and a button for each of the three channels, with each direct pack's price per 1,000 requests and the per-second add-ons.
    • The home page's code panel is labelled as a recorded sample, with its capture date, until you press play; then it shows the live response with its status and latency.
    • Wherever the demo stops — a rate limit, a 401 or a 403 — the page offers a key, and the dock says when the demo allowance resets. A successful run ends with a next step.
    • The guides were re-checked: batch caps come from the spec, the migration guide covers Spotify's March and July 2026 changes, the Apify guide links the play-count endpoints and prints the prices in force, and the Python SDK page documents 2.0.1.
    • /charts keeps the last live chart on disk, so a deploy or a restart no longer drops it back to the recorded sample.
    • The reference pages of the operations 1.2.0 retired answer a permanent redirect to the nearest page that still exists.
    • Key holders get a way back: the topbar links the direct-key dashboard, and the footer adds usage, renewal and the service status page.

  3. Endpoint reference synced to API 1.2.0

    The endpoint reference documents version 1.2.0 of the public OpenAPI spec: 105 endpoints, 119 operations in 23 groups. Three operations arrived, seven operator-only tools left the public spec, and 52 operations gained or changed parameters or a request body.

    API

    • Added GET /status: a public status summary per endpoint family, also served without a key at /status.json on the API host.
    • Added GET /tracks/{id}: one track, the same object Spotify's GET /v1/tracks/{id} returns.
    • Added GET /partner/tracks/count: lifetime play counts for a list of tracks in one call.
    • Removed from the public spec: the operator-only cache and credentials tools (GET /cache/stats, POST /cache/invalidate, GET /credentials/status, GET /cookies/redis) and three health tools (GET /health/proxies, POST /health/proxies/clear, POST /health/clear-errors).
    • Deprecated in favour of /status: GET /health/instance, GET /health/cluster and GET /health/cluster/strict.
    • New parameters: the AI GETs take artistId, question, genre and whatever else each analysis needs; /tracking/* reads spotifyId and spotifyType; /top_artists, /top_albums and /viral_tracks gained the past date /top_200_tracks already had, and /top_200_tracks gained city.

    Site

    • Reference pages for the three new operations, and parameter tables that list what each changed operation now takes.
    • Page titles, social cards and the command palette read every count from the spec instead of typing it; llms.txt and the RSS feed are static files, and a test holds their counts to the spec.

  4. Four guides, a guides hub, and pages that paint before they hydrate

    Guides to monthly listeners, audio features after the 2024 deprecation, rate limits and the Apify scraper, all on a new /guides hub; and a loading rework after which Lighthouse measured 97 to 100 on mobile across the site, up from 67 to 88.

    Site

    • Four guides: monthly listeners, audio features after the 2024 deprecation, rate limits, and the Spotify scraper on Apify. /guides lists every guide, and each guide ends with the others.
    • Pages paint before the app hydrates: the stylesheet is inlined, the scripts load a frame after the first paint, and icons are drawn inline instead of by a 52 KB icon runtime.
    • Visitors arriving from a search or a bookmark, and search engines' crawlers, get the charts, artist and album pages rendered on the server; the demo's own gate had been refusing those renders.
    • /charts falls back to the recorded Top 200, labelled with its capture date, when the live chart is slow, and every operation page states the free tier and the direct price.

  5. A social card for every URL, and guides to lyrics and charts

    Every indexable URL got its own 1200×630 social card, drawn at build time from the spec, so a link to an operation stopped unfurling as the same picture as a link to /pricing. Two guides covered the two things the Web API has no endpoint for.

    Site

    • One card per page, per endpoint group and per operation, each operation's printing its real method and path.
    • /spotify-lyrics-api: why the Web API has no lyrics endpoint, what a line-synced response contains, and lyrics as LRC or SRT files.
    • /spotify-charts-api: the chart endpoints, and what a chart row carries — rank movement, stream counts and credits.
    • /endpoints links every guide from a section of its own.

  6. A page for every operation, a command palette, and pricing and SDK pages

    The reference stopped being one long page. Every endpoint group and every operation got a server-rendered URL of its own, with its parameters, curl, JavaScript and Python, its recorded sample or a live-only panel, and what it answers when a request fails.

    Site

    • /endpoints/{group} and /endpoints/{group}/{operation}, all in the sitemap; the /endpoints overview lists every operation, with a filter.
    • A command palette on Ctrl+K, ⌘K or /, reaching every page, group and operation.
    • /pricing works out the cost per 1,000 requests on each channel at four volumes, and /sdk/node and /sdk/python document the published packages.
    • Two migration guides: the Spotify Web API alternative, and the Spotify API without OAuth.

  7. A Spotify-style redesign around one action: run a real request

    The site was rebuilt on a Spotify-like shell — a left rail, a rounded content pane and a dock along the bottom — around one action: press play on an endpoint and read the real response.

    Site

    • A console dock on every page runs the request and shows its status and latency; when the demo is rate-limited it shows a recorded sample, labelled with its capture date.
    • The endpoint reference, rebuilt on the OpenAPI spec, with a Run button on every operation.
    • One search across endpoints, pages and the Spotify catalog.
    • A player bar, and a now-playing sheet with synced lyrics and audio features.
    • Figtree and JetBrains Mono, self-hosted, and one set of colour tokens on every page.

Follow the next release

The RSS feed carries each release from 21 October 2026 on, under the title and date it has here, and each guide as it is published. The API's own record of its operations is its OpenAPI spec.

RSS feed openapi.json (opens in a new tab)