Deezer icon

Deezer

Access public song data via the Deezer API
Join our community

Actions43

Overview

This node interacts with the Deezer API to retrieve data related to music content. Specifically, for the Album resource and the Get Tracks operation, it fetches the list of tracks contained within a specified album by its ID. This is useful when you want to obtain detailed track information from an album, such as track titles, durations, and other metadata.

Common scenarios include:

  • Building playlists or libraries based on album contents.
  • Displaying track lists in music apps or dashboards.
  • Analyzing album compositions or exporting track data.

Example: Given an album ID, the node returns all or a subset of tracks from that album, supporting pagination through offset and limit parameters.

Properties

Name Meaning
Resource ID The unique identifier of the album whose tracks you want to retrieve.
Return All Whether to return all tracks from the album or only up to a specified limit.
Offset The starting position (zero-based) in the list of tracks from which to begin retrieval.
Limit The maximum number of tracks to return if not returning all.

Output

The output is a JSON array where each element represents a track object from the specified album. Each track object contains metadata fields as provided by the Deezer API, such as track title, duration, artist info, and more.

If binary data were involved (e.g., audio files), it would be summarized here, but this node only outputs JSON metadata about tracks.

Dependencies

  • Requires an OAuth2 API credential for Deezer to authenticate requests.
  • Uses the Deezer public API endpoint https://api.deezer.com.
  • Requires network access to Deezer's API.
  • The node internally uses helper functions to handle authentication token retrieval and API requests.

Troubleshooting

  • Invalid or missing Album ID: Ensure the "Resource ID" property is correctly set to a valid album ID; otherwise, the API will return an error.
  • Authentication errors: Verify that the OAuth2 credentials are properly configured and have valid tokens.
  • Rate limiting or API errors: Deezer may throttle requests; consider handling retries or reducing request frequency.
  • Pagination issues: If "Return All" is false, ensure "Limit" and "Offset" are set appropriately to avoid missing data.
  • Network connectivity: Confirm that the node can reach Deezer's API endpoint without firewall or proxy issues.

Common error messages typically relate to invalid IDs, expired tokens, or network failures. Resolving these involves checking input values, refreshing credentials, and ensuring stable internet connection.

Links and References

Discussion