New Public Playlist treated as Private by the API

[notkvsr]

Plan

Premium

Country

US

New playlists created via client software (both desktop and iOS) display as Public in the UI but are treated as Private by the API. They do not return on endpoints like /me/playlists without the 'playlist-read-private' scope and when returned via that scope or via /v1/playlists/{playlist_id} they return "public": false every time.

I'm likely missing something here but could someone explain this discrepancy?

[Ximzend]

The variable public is only true when a playlist is publicly displayed on someone's profile.

[notkvsr]

Thank you for your response - do you know if there's any information available as to why the concept of being "public" is not consistent between Client and API?

[Ximzend · Accepted solution]

Before all playlists that were not on your profile were called private, but they were not really private. Now they changed that name to public, and made a new option that they called private, and did not change anything on the API side. Therefore public is still on profile, and private is still not on profile.

[notkvsr]

Thank you so much!