# Spotify Details API (spotify.profile)

- Canonical page: [https://everyinfra.com/en/spotify-api/profile](https://everyinfra.com/en/spotify-api/profile?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "spotify", "action": "profile", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: single object
- Mode: sync; add "mode": "async" for slow tasks

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.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=spotify&action=profile

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | 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. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
| url | Link to the record on the platform. |
| name | Name of the object itself, for account, product and business capabilities. |
| type | Record type; values depend on the capability (for example video / image / text). |
| release_date | platform-native meaning |
| label | platform-native meaning |
| artists | platform-native meaning |
| image_url | Image link. Capabilities with several images may return an image_urls array. |
| track_count | platform-native meaning |
| tracks | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |

## Example

```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>"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "spotify",
        "action": "profile",
        "params": {
            "url": "https://open.spotify.com/album/<ALBUM_ID>",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

No real sample for these example parameters yet: structure only, every value is a placeholder (…).

```text
{
  "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": { … }
}
```

## 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.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=spotify
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
