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 Fans operation, it fetches a list of users who are fans of a particular album. This can be useful in scenarios where you want to analyze or engage with an album's audience, such as marketing campaigns, fan engagement analytics, or personalized recommendations.

For example, a music app could use this node to display the most engaged listeners of an album or to gather insights about the demographics of an album’s fanbase.

Properties

Name Meaning
Resource ID The unique identifier of the album whose fans you want to retrieve (e.g., "1234567").
Return All Whether to return all fans or limit the number of results returned.
Offset The starting position in the list of fans from which to begin returning results (default 0).
Limit The maximum number of fan records to return if not returning all (default 50).

Output

The output is a JSON array where each element represents a user object corresponding to a fan of the specified album. Each user object contains details about the fan as provided by the Deezer API.

If the Return All property is set to true, the node will paginate through all available fans and return the complete list; otherwise, it returns up to the specified limit starting from the offset.

No binary data is output by this node.

Dependencies

  • Requires an OAuth2 API credential for Deezer to authenticate requests.
  • Uses the Deezer public API endpoint: https://api.deezer.com.
  • The node internally obtains an access token using the provided credentials before making API calls.
  • No additional environment variables or external services are required beyond the Deezer OAuth2 credential.

Troubleshooting

  • Common issues:

    • Invalid or expired OAuth2 credentials may cause authentication failures.
    • Providing an incorrect or non-existent album ID will result in errors or empty results.
    • Requesting too many results without pagination (Return All false but high Limit) might lead to incomplete data.

  • Error messages:

    • Errors from the Deezer API (e.g., "Invalid access token", "Resource not found") will be returned in the output JSON under an error field.
    • Network or request errors will throw exceptions unless the node is configured to continue on failure, in which case error details are included in the output.

  • Resolution tips:

    • Ensure the OAuth2 credentials are valid and refreshed.
    • Verify the album ID exists on Deezer.
    • Use pagination properties (Offset and Limit) appropriately or enable Return All to get full data sets.

Links and References

Discussion