POST

API health

24h health
Normal
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Last 24 hours

Last 30 days

Look up an album or single on Spotify from its full link. Get the release type, date, record label, credited artists, cover and track list. This older entry point reads releases, not user profiles. It plays no audio.

Send POST https://api.everyinfra.com/api/v1/social with platform set to spotify and action set to profile. Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

Spotify Details reads the release information of one album or single from its full open.spotify.com link and returns the name, the kind of release, release date, record label, credited artists, cover image, track count and track list. It is the older Spotify entry point and reads releases, not user profiles. Use it to confirm a record's label and release date before you license, pitch or catalog it, or to list a release's tracks for analysis.

Pass the complete link, such as https://open.spotify.com/album/<album ID>. Unlike the Spotify Track, Album and Artist details capabilities, Details does not take a spotify: URI or a bare ID. type says what kind of release the link points to, label is the record company and release_date the date as Spotify lists it. For an artist page, use Spotify Artist details instead.

AI prompt

#
Please help me write a data collection script with the EveryInfra Spotify Details endpoint (spotify/profile).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to spotify and action to profile, and put the parameters inside params.
- Required parameters:
  - url: Specifies the target open.spotify.com link, spotify:type:ID URI, or raw entity ID corresponding to the chosen action (artist, track, album, or playlist).
- Returns one object. Main fields: id, url, name, type, release_date, label, artists, image_url, track_count, tracks.
- Example request body:
{
  "platform": "spotify",
  "action": "profile",
  "params": {
    "url": "https://open.spotify.com/album/<ALBUM_ID>"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesspotifyPlatform identifier, fixed value.
actionbodystringYesprofileCapability identifier, fixed value.
urlbody.paramsstringYes-Specifies the target open.spotify.com link, spotify:type:ID URI, or raw entity ID corresponding to the chosen action (artist, track, album, or playlist). Input types must match the endpoint action and cannot be interchanged. Legacy profile endpoints accept full Spotify links to return album and single streaming metadata rather than user profile account details.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "spotify",
  "action": "profile",
  "params": {
    "url": "https://open.spotify.com/album/<ALBUM_ID>"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
json
{  "id": "req_…",  "platform": "spotify",  "action": "profile",  "results": {    "id": …,    "url": …,    "name": …,    "type": …,    "release_date": …,    "label": …,    "artists": …,    "image_url": …,    "track_count": …,    "tracks": …,    "platform": …  },  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
urlLink to the record on the platform.
nameName of the object itself, for account, product and business capabilities.
typeRecord type; values depend on the capability (for example video / image / text).
release_dateKeeps the platform's own meaning
labelKeeps the platform's own meaning
artistsKeeps the platform's own meaning
image_urlImage link. Capabilities with several images may return an image_urls array.
track_countKeeps the platform's own meaning
tracksKeeps the platform's own meaning
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

#

Can I read a Spotify user's profile with Details?

#

No. Despite the word profile in this page's address, Details reads release information for an album or single: name, label, release date, credited artists and tracks. Spotify listener accounts are not part of it. For an artist's page, with listeners, followers and top tracks, use Spotify Artist details.

Which link formats does Details accept?

#

Only the full open.spotify.com link to the album or single. If you hold a spotify: URI or a bare ID, use the Spotify Album or Track capability, which accept those forms as well as full links.

How do I read the tracks on a release?

#

tracks lists them and track_count gives how many there are. artists names everyone credited on the release, which can be more than one artist. For one track's own details, use the Spotify Track capability with that track's link.

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Official references

#

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • Spotify: Resource URLs, URIs, and User Identifiers Cannot Be Interchanged ↗

    Official Spotify documentation distinguishes resource URLs, URIs, IDs, and user identifiers. The legacy `profile` action only accepts full release history URLs; despite name similarity, it does not function as an official user profile endpoint, nor does it automatically parse URIs for other actions.

    Checked 2026-09-04

Google Analytics needs consent. Privacy