GET
TracksGet Audio Features
Return acoustic and rhythmic feature signals for a track.
/v1/tracks/:tune_id/featuresMethod
GET
Path
/v1/tracks/:tune_id/features
Group
Tracks
Overview
How to use this endpoint
Use this endpoint when you need structured API data in a predictable JSON shape. Reference the request example, required parameters, and response fields below to wire it into your product or internal tool.
Response format
JSON response
All successful responses return data in a stable JSON envelope and use Tune UUIDs for resource identifiers.
Code example
Example request
request
Copy-ready
GET /v1/tracks/3f2504e0-4f89-11d3-9a0c-0305e82c3301/featuresRequest parameters
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
tune_id | uuid | Yes | Stable Tune identifier for the requested resource. |
Response schema
Response fields
| Field | Type | Description |
|---|---|---|
tune_id | uuid | Track Tune identifier. |
acousticness | float | Confidence that the track is acoustic. |
danceability | float | How suitable the track is for dancing. |
energy | float | Perceptual measure of intensity and activity. |
instrumentalness | float | Likelihood of no vocals. |
key | integer | Musical key, 0 through 11. |
liveness | float | Likelihood the track was performed live. |
loudness | float | Overall loudness in decibels. |
mode | integer | 1 for major, 0 for minor. |
speechiness | float | Presence of spoken words. |
tempo | float | Estimated tempo in BPM. |
time_signature | integer | Estimated time signature. |
valence | float | Musical positiveness from 0 to 1. |
duration_ms | integer | Track duration in milliseconds. |
Code example
Example response
application/json
Copy-ready
{
"data": {
"tune_id": "3f2504e0-4f89-11d3-9a0c-0305e82c3301",
"acousticness": 0.12,
"danceability": 0.78,
"energy": 0.91,
"instrumentalness": 0.42,
"key": 5,
"liveness": 0.09,
"loudness": -5.4,
"mode": 0,
"speechiness": 0.04,
"tempo": 128,
"time_signature": 4,
"valence": 0.65,
"duration_ms": 243187
}
}Next steps